domain/json.ng
- Registration data
RDAP - DNS records
A, AAAA, MX, NS, TXT, CAA, SOA - Email policy
_dmarc - TLS certificate
port 443 - Website snapshot
HTTP - Comparing with history
whois.is archive
RDAPA, AAAA, MX, NS, TXT, CAA, SOA_dmarcport 443HTTPwhois.is archivejson.ng was registered in January 2025 with TRUEHOST CLOUD, and is due to expire in January 2027. Its website was online at the last check. json.ng doesn't receive email: it publishes no mail servers. The website presents it as JSON Review (local json table viewer).
Based on what we observed, it publishes no email authentication records.
The last check failed. The operation was aborted due to timeout. What follows is the most recent evidence we hold.
| Type | Value |
|---|---|
| A | 104.21.96.133 |
| A | 172.67.180.254 |
| AAAA | 2606:4700:3031::ac43:b4fe |
| AAAA | 2606:4700:3033::6815:6085 |
| NS | marjory.ns.cloudflare.com |
| NS | simon.ns.cloudflare.com |
| SOA | marjory.ns.cloudflare.com dns.cloudflare.com 2420027911 |
We couldn't place this site's addresses on a network.
A network is whoever runs the servers behind the address. With a CDN such as Cloudflare in front, that is the CDN, not the company hosting the site behind it.
Read from the homepage's code and server headers. Sites can hide what they use, so this list may be incomplete.
No public prices on the pages we read.
Every value is quoted from the page linked beside it. Read from 1 page.
First observation recorded. Every change from here on is preserved and shown here.
Most registries now keep the registrant's details private, and whois.is doesn't show them. json.ng is registered through TRUEHOST CLOUD. The website presents itself as JSON Review; that is the site's own claim, not a verified owner.
json.ng was registered on 30 Jan 2025, making it 1 year old.
The registry lists 30 Jan 2027 as the expiry date, 70 days from now. Most domains renew automatically before then.
No one: json.ng publishes no MX records, so it can't receive email.
It was up when we last checked, 6 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.