A small tool to view real-world ActivityPub objects as JSON! Enter a URL
or username from Mastodon or a similar service below, and we'll send a
request with
the right
Accept
header
to the server to view the underlying object.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
{
"ostatus": "http://ostatus.org#",
"atomUri": "ostatus:atomUri",
"inReplyToAtomUri": "ostatus:inReplyToAtomUri",
"conversation": "ostatus:conversation",
"sensitive": "as:sensitive",
"toot": "http://joinmastodon.org/ns#",
"votersCount": "toot:votersCount",
"litepub": "http://litepub.social/ns#",
"directMessage": "litepub:directMessage",
"Hashtag": "as:Hashtag"
}
],
"id": "https://infosec.exchange/users/JayeLTee/statuses/113509784680044454",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2024-11-19T13:11:00Z",
"url": "https://infosec.exchange/@JayeLTee/113509784680044454",
"attributedTo": "https://infosec.exchange/users/JayeLTee",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/JayeLTee/followers",
"https://xn--baw-joa.social/users/lfdi"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/JayeLTee/statuses/113509784680044454",
"inReplyToAtomUri": null,
"conversation": "tag:infosec.exchange,2024-11-19:objectId=214563984:objectType=Conversation",
"content": "<p>Update on the 180+ German Fire Departments(Fireplan.de) exposed servers I found and reported to <span class=\"h-card\" translate=\"no\"><a href=\"https://xn--baw-joa.social/@lfdi\" class=\"u-url mention\">@<span>lfdi</span></a></span><br /> <br />So over the last 2 days I've been contacted by multiple fire departments asking me to verify if they were affected or not on my recent find. 5 out of 5 were on it, from what I can tell most if not all of the ones who reached out so far were told by Fireplan they weren't affected.</p><p>I didn't release the 180+ department names I found because I know 100% I haven't found every single one of them and me giving a list would be a great excuse for the company to base it off the list and ignore every single one I didn't find.</p><p>I'm not releasing the list but I'm gonna say again what I initially said on my post:</p><p>It's more than likely that every single server was set the same way, so if you used Fireplan and people uploaded files/pictures to it, your data was probably exposed.<br />Also I've been told some timeline of exposure that is laughable, I checked the oldest logs I have for this service and the servers were exposed back then too, in December 2023.</p><p>I also updated the original post, for anyone who is wondering what I'm talking about it's this: <a href=\"https://jltee.substack.com/p/putting-out-virtual-fires-in-germany\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">jltee.substack.com/p/putting-o</span><span class=\"invisible\">ut-virtual-fires-in-germany</span></a></p><p><a href=\"https://infosec.exchange/tags/cybersecurity\" class=\"mention hashtag\" rel=\"tag\">#<span>cybersecurity</span></a> <a href=\"https://infosec.exchange/tags/infosec\" class=\"mention hashtag\" rel=\"tag\">#<span>infosec</span></a> <a href=\"https://infosec.exchange/tags/germany\" class=\"mention hashtag\" rel=\"tag\">#<span>germany</span></a> <a href=\"https://infosec.exchange/tags/dataleak\" class=\"mention hashtag\" rel=\"tag\">#<span>dataleak</span></a> <a href=\"https://infosec.exchange/tags/leak\" class=\"mention hashtag\" rel=\"tag\">#<span>leak</span></a> <a href=\"https://infosec.exchange/tags/feuerwehr\" class=\"mention hashtag\" rel=\"tag\">#<span>feuerwehr</span></a></p>",
"contentMap": {
"en": "<p>Update on the 180+ German Fire Departments(Fireplan.de) exposed servers I found and reported to <span class=\"h-card\" translate=\"no\"><a href=\"https://xn--baw-joa.social/@lfdi\" class=\"u-url mention\">@<span>lfdi</span></a></span><br /> <br />So over the last 2 days I've been contacted by multiple fire departments asking me to verify if they were affected or not on my recent find. 5 out of 5 were on it, from what I can tell most if not all of the ones who reached out so far were told by Fireplan they weren't affected.</p><p>I didn't release the 180+ department names I found because I know 100% I haven't found every single one of them and me giving a list would be a great excuse for the company to base it off the list and ignore every single one I didn't find.</p><p>I'm not releasing the list but I'm gonna say again what I initially said on my post:</p><p>It's more than likely that every single server was set the same way, so if you used Fireplan and people uploaded files/pictures to it, your data was probably exposed.<br />Also I've been told some timeline of exposure that is laughable, I checked the oldest logs I have for this service and the servers were exposed back then too, in December 2023.</p><p>I also updated the original post, for anyone who is wondering what I'm talking about it's this: <a href=\"https://jltee.substack.com/p/putting-out-virtual-fires-in-germany\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">jltee.substack.com/p/putting-o</span><span class=\"invisible\">ut-virtual-fires-in-germany</span></a></p><p><a href=\"https://infosec.exchange/tags/cybersecurity\" class=\"mention hashtag\" rel=\"tag\">#<span>cybersecurity</span></a> <a href=\"https://infosec.exchange/tags/infosec\" class=\"mention hashtag\" rel=\"tag\">#<span>infosec</span></a> <a href=\"https://infosec.exchange/tags/germany\" class=\"mention hashtag\" rel=\"tag\">#<span>germany</span></a> <a href=\"https://infosec.exchange/tags/dataleak\" class=\"mention hashtag\" rel=\"tag\">#<span>dataleak</span></a> <a href=\"https://infosec.exchange/tags/leak\" class=\"mention hashtag\" rel=\"tag\">#<span>leak</span></a> <a href=\"https://infosec.exchange/tags/feuerwehr\" class=\"mention hashtag\" rel=\"tag\">#<span>feuerwehr</span></a></p>"
},
"updated": "2024-11-19T13:23:57Z",
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://xn--baw-joa.social/users/lfdi",
"name": "@lfdi@xn--baw-joa.social"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/cybersecurity",
"name": "#cybersecurity"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/infosec",
"name": "#infosec"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/germany",
"name": "#germany"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/dataleak",
"name": "#dataleak"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/leak",
"name": "#leak"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/feuerwehr",
"name": "#feuerwehr"
}
],
"replies": {
"id": "https://infosec.exchange/users/JayeLTee/statuses/113509784680044454/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/JayeLTee/statuses/113509784680044454/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/JayeLTee/statuses/113509784680044454/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/JayeLTee/statuses/113509784680044454/likes",
"type": "Collection",
"totalItems": 15
},
"shares": {
"id": "https://infosec.exchange/users/JayeLTee/statuses/113509784680044454/shares",
"type": "Collection",
"totalItems": 15
}
}