domain/c0d3f0rg3.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 archivec0d3f0rg3.com was registered in September 2025 with Registrar.eu, and is due to expire in September 2028. Its website was online at the last check, served from Hostinger International's network. Email for c0d3f0rg3.com is handled by Hostinger.
Registered 1 year ago. The website responds, SPF and DMARC are published and the certificate is trusted.
| Type | Value |
|---|---|
| A | 92.113.16.56 AS47583 · Hostinger International Limited · UA |
| A | 92.113.23.255 AS47583 · Hostinger International Limited · UA |
| AAAA | 2a02:4780:84:81b5:cd3a:c26b:6d05:7543 AS47583 · Hostinger International Limited · LT |
| AAAA | 2a02:4780:84:b517:1f9b:461:ea1:8744 AS47583 · Hostinger International Limited · LT |
| MX | 10 mx2.hostinger.com |
| MX | 5 mx1.hostinger.com |
| NS | ns1.dns-parking.com |
| NS | ns2.dns-parking.com |
| TXT | v=spf1 include:_spf.mail.hostinger.com ~all |
| DMARC | v=DMARC1; p=none |
| SOA | ns1.dns-parking.com dns.hostinger.com 2026111901 |
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), so we can't read its business details.
Most registries now keep the registrant's details private, and whois.is doesn't show them. c0d3f0rg3.com is registered through Registrar.eu.
c0d3f0rg3.com was registered on 13 Sept 2025, making it 1 year old.
The registry lists 13 Sept 2028 as the expiry date, 663 days from now. Most domains renew automatically before then.
c0d3f0rg3.com's website is served from Hostinger International's network.
Email for c0d3f0rg3.com is handled by Hostinger, according to its MX records.
It was up when we last checked, 16 hours ago (21 Nov 2026), answering with HTTP 403. That shows how it was then, not a guarantee of right now.