domain/foreveryou.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 archiveforeveryou.ng was registered in April 2025 with TRUEHOST CLOUD, and is due to expire in April 2027. Its website was online at the last check. Email for foreveryou.ng is handled by migadu.com. The website presents it as foreveryou.ng (mastodon server).
Registered 2 years ago. The website responds, SPF and DMARC are published and the certificate is trusted.
The last check failed. RDAP returned 502 for foreveryou.ng. What follows is the most recent evidence we hold.
| Type | Value |
|---|---|
| A | 82.64.236.139 |
| MX | 10 aspmx1.migadu.com |
| MX | 20 aspmx2.migadu.com |
| NS | ns1.vercel-dns.com |
| NS | ns2.vercel-dns.com |
| TXT | hosted-email-verify=ov0288oz |
| TXT | v=spf1 include:spf.migadu.com -all |
| CAA | 0 issue "letsencrypt.org" |
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.
We didn't recognise any technology on the homepage.
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. foreveryou.ng is registered through TRUEHOST CLOUD. The website presents itself as foreveryou.ng; that is the site's own claim, not a verified owner.
foreveryou.ng was registered on 21 Apr 2025, making it 1 year old.
The registry lists 21 Apr 2027 as the expiry date, 152 days from now. Most domains renew automatically before then.
Email for foreveryou.ng is handled by migadu.com, according to its MX records.
It was up when we last checked, 3 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.
| CAA |
| 0 issue "pki.goog" |
| CAA | 0 issue "sectigo.com" |
| DMARC | v=DMARC1; p=quarantine; |
| SOA | ns1.vercel-dns.com hostmaster.nsone.net 1745281156 |