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/resingm/statuses/111182874175674411/activity",
"type": "Create",
"actor": "https://infosec.exchange/users/resingm",
"published": "2023-10-05T14:27:04Z",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/resingm/followers"
],
"object": {
"id": "https://infosec.exchange/users/resingm/statuses/111182874175674411",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2023-10-05T14:27:04Z",
"url": "https://infosec.exchange/@resingm/111182874175674411",
"attributedTo": "https://infosec.exchange/users/resingm",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/resingm/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/resingm/statuses/111182874175674411",
"inReplyToAtomUri": null,
"conversation": "tag:infosec.exchange,2023-10-05:objectId=100273474:objectType=Conversation",
"content": "<p>Today, I read about some old piece of news: In 2020, <a href=\"https://infosec.exchange/tags/Mozilla\" class=\"mention hashtag\" rel=\"tag\">#<span>Mozilla</span></a> decided to implement a new <a href=\"https://infosec.exchange/tags/security\" class=\"mention hashtag\" rel=\"tag\">#<span>security</span></a> feature - namely <a href=\"https://infosec.exchange/tags/DoH\" class=\"mention hashtag\" rel=\"tag\">#<span>DoH</span></a> by default. Apparently, that \"security\" feature means, that the locally configured <a href=\"https://infosec.exchange/tags/DNS\" class=\"mention hashtag\" rel=\"tag\">#<span>DNS</span></a> resolver will be bypassed and DNS lookups are performed over <a href=\"https://infosec.exchange/tags/HTTPS\" class=\"mention hashtag\" rel=\"tag\">#<span>HTTPS</span></a>, i.e. indistinguishable from regular TLS-encrypted web traffic. Instead, US-based users could choose between either \"Cloudflare and NextDNS - both wich are trusted resolvers\". Users had to opt-out of it. A firewall would have no chance to block that DNS traffic and users involuntarily will be using Cloudflare's DNS, since this is the default option.</p><p>Wow. Just wow. </p><p>Is anyone aware of any updates on this?</p><p><a href=\"https://blog.mozilla.org/en/products/firefox/firefox-continues-push-to-bring-dns-over-https-by-default-for-us-users/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">blog.mozilla.org/en/products/f</span><span class=\"invisible\">irefox/firefox-continues-push-to-bring-dns-over-https-by-default-for-us-users/</span></a></p>",
"contentMap": {
"en": "<p>Today, I read about some old piece of news: In 2020, <a href=\"https://infosec.exchange/tags/Mozilla\" class=\"mention hashtag\" rel=\"tag\">#<span>Mozilla</span></a> decided to implement a new <a href=\"https://infosec.exchange/tags/security\" class=\"mention hashtag\" rel=\"tag\">#<span>security</span></a> feature - namely <a href=\"https://infosec.exchange/tags/DoH\" class=\"mention hashtag\" rel=\"tag\">#<span>DoH</span></a> by default. Apparently, that \"security\" feature means, that the locally configured <a href=\"https://infosec.exchange/tags/DNS\" class=\"mention hashtag\" rel=\"tag\">#<span>DNS</span></a> resolver will be bypassed and DNS lookups are performed over <a href=\"https://infosec.exchange/tags/HTTPS\" class=\"mention hashtag\" rel=\"tag\">#<span>HTTPS</span></a>, i.e. indistinguishable from regular TLS-encrypted web traffic. Instead, US-based users could choose between either \"Cloudflare and NextDNS - both wich are trusted resolvers\". Users had to opt-out of it. A firewall would have no chance to block that DNS traffic and users involuntarily will be using Cloudflare's DNS, since this is the default option.</p><p>Wow. Just wow. </p><p>Is anyone aware of any updates on this?</p><p><a href=\"https://blog.mozilla.org/en/products/firefox/firefox-continues-push-to-bring-dns-over-https-by-default-for-us-users/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">blog.mozilla.org/en/products/f</span><span class=\"invisible\">irefox/firefox-continues-push-to-bring-dns-over-https-by-default-for-us-users/</span></a></p>"
},
"updated": "2023-10-05T14:33:05Z",
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/mozilla",
"name": "#mozilla"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/security",
"name": "#security"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/doh",
"name": "#doh"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/dns",
"name": "#dns"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/https",
"name": "#https"
}
],
"replies": {
"id": "https://infosec.exchange/users/resingm/statuses/111182874175674411/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/resingm/statuses/111182874175674411/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/resingm/statuses/111182874175674411/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/resingm/statuses/111182874175674411/likes",
"type": "Collection",
"totalItems": 2
},
"shares": {
"id": "https://infosec.exchange/users/resingm/statuses/111182874175674411/shares",
"type": "Collection",
"totalItems": 0
}
}
}