domain/retrogami.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 archiveretrogami.ng was registered in March 2023 with TRUEHOST CLOUD, and is due to expire in March 2027. Its website was online at the last check, served from Cloudflare's network. retrogami.ng doesn't receive email: it publishes no mail servers.
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.10.35 AS13335 · Cloudflare, Inc. · US |
| A | 172.67.189.228 AS13335 · Cloudflare, Inc. · US |
| AAAA | 2606:4700:3036::6815:a23 AS13335 · Cloudflare, Inc. · US |
| AAAA | 2606:4700:3036::ac43:bde4 AS13335 · Cloudflare, Inc. · US |
| NS | aron.ns.cloudflare.com |
| NS | woz.ns.cloudflare.com |
| SOA | aron.ns.cloudflare.com dns.cloudflare.com 2418508068 |
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.
We didn't recognise any technology on the homepage.
The site blocks automated reading (HTTP 403, Cloudflare challenge), so we can't read its business details.
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. retrogami.ng is registered through TRUEHOST CLOUD.
retrogami.ng was registered on 25 Mar 2023, making it 3 years old.
The registry lists 25 Mar 2027 as the expiry date, 125 days from now. Most domains renew automatically before then.
retrogami.ng is served through Cloudflare, which sits in front of the site. The company hosting the site behind it isn't visible from outside.
No one: retrogami.ng publishes no MX records, so it can't receive email.
It was up when we last checked, 5 hours ago (21 Nov 2026), answering with HTTP 403. That shows how it was then, not a guarantee of right now.