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/114336641343837545",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2025-04-14T13:51:32Z",
"url": "https://infosec.exchange/@resingm/114336641343837545",
"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/114336641343837545",
"inReplyToAtomUri": null,
"conversation": "tag:infosec.exchange,2025-04-14:objectId=261530119:objectType=Conversation",
"content": "<p>Just wanted to share some thoughts on <a href=\"https://infosec.exchange/tags/RFC9715\" class=\"mention hashtag\" rel=\"tag\">#<span>RFC9715</span></a> - an <a href=\"https://infosec.exchange/tags/RFC\" class=\"mention hashtag\" rel=\"tag\">#<span>RFC</span></a> that defines standards on reducing the <a href=\"https://infosec.exchange/tags/DNS\" class=\"mention hashtag\" rel=\"tag\">#<span>DNS</span></a> issue of IP fragmentation over <a href=\"https://infosec.exchange/tags/UDP\" class=\"mention hashtag\" rel=\"tag\">#<span>UDP</span></a>. It's not a long read, but a good one for everyone who understands the issues of large UDP responses on the <a href=\"https://infosec.exchange/tags/Internet\" class=\"mention hashtag\" rel=\"tag\">#<span>Internet</span></a>. A great leap forward to (hopefully) reduce the reflection/amplification <a href=\"https://infosec.exchange/tags/DDoS\" class=\"mention hashtag\" rel=\"tag\">#<span>DDoS</span></a> potential of DNS.</p><p>Just today I learned that <a href=\"https://infosec.exchange/tags/Google\" class=\"mention hashtag\" rel=\"tag\">#<span>Google</span></a> will configure their public DNS resolvers to limit to ~1400 bytes (smaller adjustments expected while figuring out the sweet spot in production). From now on, DNS responses which exceed this limit will have the truncated flag set instructing the client to resolve back to <a href=\"https://infosec.exchange/tags/TCP\" class=\"mention hashtag\" rel=\"tag\">#<span>TCP</span></a>. </p><p><a href=\"https://infosec.exchange/tags/ipv4\" class=\"mention hashtag\" rel=\"tag\">#<span>ipv4</span></a> <a href=\"https://infosec.exchange/tags/ipv6\" class=\"mention hashtag\" rel=\"tag\">#<span>ipv6</span></a> <a href=\"https://infosec.exchange/tags/ietf\" class=\"mention hashtag\" rel=\"tag\">#<span>ietf</span></a></p>",
"contentMap": {
"en": "<p>Just wanted to share some thoughts on <a href=\"https://infosec.exchange/tags/RFC9715\" class=\"mention hashtag\" rel=\"tag\">#<span>RFC9715</span></a> - an <a href=\"https://infosec.exchange/tags/RFC\" class=\"mention hashtag\" rel=\"tag\">#<span>RFC</span></a> that defines standards on reducing the <a href=\"https://infosec.exchange/tags/DNS\" class=\"mention hashtag\" rel=\"tag\">#<span>DNS</span></a> issue of IP fragmentation over <a href=\"https://infosec.exchange/tags/UDP\" class=\"mention hashtag\" rel=\"tag\">#<span>UDP</span></a>. It's not a long read, but a good one for everyone who understands the issues of large UDP responses on the <a href=\"https://infosec.exchange/tags/Internet\" class=\"mention hashtag\" rel=\"tag\">#<span>Internet</span></a>. A great leap forward to (hopefully) reduce the reflection/amplification <a href=\"https://infosec.exchange/tags/DDoS\" class=\"mention hashtag\" rel=\"tag\">#<span>DDoS</span></a> potential of DNS.</p><p>Just today I learned that <a href=\"https://infosec.exchange/tags/Google\" class=\"mention hashtag\" rel=\"tag\">#<span>Google</span></a> will configure their public DNS resolvers to limit to ~1400 bytes (smaller adjustments expected while figuring out the sweet spot in production). From now on, DNS responses which exceed this limit will have the truncated flag set instructing the client to resolve back to <a href=\"https://infosec.exchange/tags/TCP\" class=\"mention hashtag\" rel=\"tag\">#<span>TCP</span></a>. </p><p><a href=\"https://infosec.exchange/tags/ipv4\" class=\"mention hashtag\" rel=\"tag\">#<span>ipv4</span></a> <a href=\"https://infosec.exchange/tags/ipv6\" class=\"mention hashtag\" rel=\"tag\">#<span>ipv6</span></a> <a href=\"https://infosec.exchange/tags/ietf\" class=\"mention hashtag\" rel=\"tag\">#<span>ietf</span></a></p>"
},
"updated": "2025-04-14T13:53:54Z",
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/rfc9715",
"name": "#rfc9715"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/rfc",
"name": "#rfc"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/dns",
"name": "#dns"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/udp",
"name": "#udp"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/internet",
"name": "#internet"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/ddos",
"name": "#ddos"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/google",
"name": "#google"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/tcp",
"name": "#tcp"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/ipv4",
"name": "#ipv4"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/ipv6",
"name": "#ipv6"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/ietf",
"name": "#ietf"
}
],
"replies": {
"id": "https://infosec.exchange/users/resingm/statuses/114336641343837545/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/resingm/statuses/114336641343837545/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/resingm/statuses/114336641343837545/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/resingm/statuses/114336641343837545/likes",
"type": "Collection",
"totalItems": 5
},
"shares": {
"id": "https://infosec.exchange/users/resingm/statuses/114336641343837545/shares",
"type": "Collection",
"totalItems": 5
}
}