domain/remcodejong.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 archiveremcodejong.com was registered in July 2005 with Cosmotown, and is due to expire in July 2027. Its website didn't respond at the last check. Email for remcodejong.com is handled by remcodejong.com.
Based on what we observed, its certificate chain does not verify and the website did not respond.
| Type | Value |
|---|---|
| A | 51.68.25.96 AS16276 · OVH SAS · FR |
| MX | 0 remcodejong.com |
| NS | ns1.cloudoon.com |
| NS | ns2.cloudoon.com |
| NS | ns3.cloudoon.org |
| TXT | v=spf1 +a +mx include:_spf.truehostcloud.com ~all |
| DMARC | v=DMARC1;p=quarantine;sp=quarantine;adkim=r;aspf=s;pct=100;fo=0;rf=afrf;ri=86400;rua=mailto:[email protected];ruf=mailto:[email protected] |
| SOA | ns1.cloudoon.com root.gra113.truehost.cloud 2026112104 |
The last check failed. fetch failed. What follows is the most recent evidence we hold.
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.
The website isn't reachable, so there is nothing to read.
No business details yet. They are read from the site's own pages, such as pricing, about and contact.
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. remcodejong.com is registered through Cosmotown.
remcodejong.com was registered on 4 Jul 2005, making it 21 years old.
The registry lists 4 Jul 2027 as the expiry date, 225 days from now. Most domains renew automatically before then.
remcodejong.com's website is served from OVH's network.
Email for remcodejong.com is handled by remcodejong.com, according to its MX records.
It didn't respond when we last checked, 5 hours ago (21 Nov 2026). That can be a short outage; check again later.