domain/tld-list.com
- 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 archivetld-list.com was registered in January 2015 with NameCheap, and is due to expire in January 2032. Its website was online at the last check, served from Cloudflare's network. Email for tld-list.com is handled by Google.
Registered 12 years ago. The website responds, DMARC is published, though SPF is not and the certificate is trusted.
| Type | Value |
|---|---|
| A | 104.20.43.237 AS13335 · Cloudflare, Inc. · US |
| A | 172.66.162.218 AS13335 · Cloudflare, Inc. · US |
| AAAA | 2606:4700:10::6814:2bed AS13335 · Cloudflare, Inc. · US |
| AAAA | 2606:4700:10::ac42:a2da AS13335 · Cloudflare, Inc. · US |
| MX | 1 smtp.google.com |
| NS | chuck.ns.cloudflare.com |
| NS | grace.ns.cloudflare.com |
| TXT | ahrefs-site-verification_1aac05f2821281886aaf00198b4000170188232d0456cedf2d07b3ed778aabbe |
| TXT | google-site-verification=ts89AH_B_D7sSBj0jnrLHiwczvZxmot50uvcoXYVgdc |
| DMARC | v=DMARC1; p=none; |
| SOA | chuck.ns.cloudflare.com dns.cloudflare.com 2420419913 |
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.
Most registries now keep the registrant's details private, and whois.is doesn't show them. tld-list.com is registered through NameCheap.
tld-list.com was registered on 2 Jan 2015, making it 11 years old.
The registry lists 2 Jan 2032 as the expiry date, 1868 days from now. Most domains renew automatically before then.
tld-list.com is served through Cloudflare, which sits in front of the site. The company hosting the site behind it isn't visible from outside.
Email for tld-list.com is handled by Google, according to its MX records.
It was up when we last checked, 15 hours ago (21 Nov 2026), answering with HTTP 403. That shows how it was then, not a guarantee of right now.