domain/dnstests.shop
- 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 archivednstests.shop was registered in July 2026 with Dynadot, and is due to expire in July 2027. Its website was online at the last check, served from OVH's network. dnstests.shop doesn't receive email: it publishes no mail servers. The website presents it as Olitt (website, e-commerce, wordpress, and domain platform).
Based on what we observed, it was registered within the last year and it publishes no email authentication records.
The last check failed. RDAP rate limit reached. What follows is the most recent evidence we hold.
| Type | Value |
|---|---|
| A | 185.113.249.232 AS16276 · OVH SAS · US |
| NS | ns1.olitt.com |
| NS | ns1.olitt.net |
| SOA | ns8.cloudoon.com hostmaster.cloudoon.com 2026091432 |
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.
Read from the homepage's code and server headers. Sites can hide what they use, so this list may be incomplete.
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. dnstests.shop is registered through Dynadot. The website presents itself as Olitt; that is the site's own claim, not a verified owner.
dnstests.shop was registered on 6 Jul 2026, making it 4 months old.
The registry lists 6 Jul 2027 as the expiry date, 228 days from now. Most domains renew automatically before then.
dnstests.shop's website is served from OVH's network.
No one: dnstests.shop publishes no MX records, so it can't receive email.
It was up when we last checked, 13 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.