ai-clean.dk

Historical scan 2026-11-08 01:23:02  ·  ← Latest scan
Zone File Timeline & History Scan Now

ai-clean.dk is a .dk domain served by 2 nameservers (ns01.one.com, ns02.one.com). It was registered on 22 November 2025 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is DNSSEC-signed and validates, has no DMARC policy and has no IPv6 address. Below are all of its DNS records from this scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

Nameservers#

2 records   61ms

A Records#

No A records found

MX Records#

No MX records found

AAAA Records (IPv6)#

No AAAA records — IPv6 not configured

HTTPS Records#

No HTTPS RR — no SVCB/HTTPS service binding

TXT Records#

1 records   259ms
TXT Record
v=spf1 -all

SPF#

PolicyRecord (ai-clean.dk)
-all (hard fail) v=spf1 -all

DMARC#

No DMARC record — mail spoofing not restricted

MTA-STS#

No MTA-STS policy — SMTP TLS not enforced

TLSRPT#

No TLSRPT record — no SMTP TLS failure reporting

CAA Records#

No CAA records — any CA may issue certificates

Web & zone#

latest probe, not this scan · checked 2026-11-19 04:37:51
wwwNXDOMAIN
www vs bare domainNeither resolves
ai-clean.dk: no address
www.ai-clean.dk: no address
WildcardNo
Denial of existenceNSEC3 · 0 iterations · no salt RFC 9276 ✓
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

DNS lookups: 0/10 · policy: -all

No problems found

TLSA / DANE#

No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

DNSSEC#

220ms
CheckResult
Validation Status Secure
AD Flag (resolver validates) Set
DS Record Found
DNSKEY Record Found
Flagsresolution failed: ncache nxrrset

SOA#

45ms
FieldValue
Serial2026110701
Primary NS (MNAME)ns01.one.com
Responsible (RNAME)hostmaster@one.com
Refresh14400s
Retry3600s
Expire1209600s
Minimum (neg-cache TTL)600s

Registration#

WHOIS fetched 2026-11-14 15:04:41
FieldValue
RegistrarONE.COM A/S
Registered2025-11-22
Expires2026-11-21 (1d)

Same registrant#

0 domains

Other .dk domains whose WHOIS registrant has the same name and postal address. Matched on a keyed hash: the registrant's details are not stored or shown. Covers only domains whose WHOIS we have fetched (refreshed about monthly).

No other domain with this registrant in our WHOIS data yet
📋 WHOIS#

Lookup Timing#

NS
61ms
A
101ms
MX
114ms
AAAA
108ms
TXT
259ms
CAA
77ms
HTTPS
112ms
TLSA
42ms
SOA
45ms
MTA-STS
136ms
DNSSEC
220ms
SRV
121ms
Total
707ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-19 04:37:51 660ms 2 NS 0 A 0 MX Secure
2026-11-17 22:51:50 357ms 2 NS 0 A 0 MX Secure
2026-11-16 15:03:24 338ms 2 NS 0 A 0 MX Secure
2026-11-14 14:56:07 336ms 2 NS 0 A 0 MX Secure
2026-11-13 14:52:59 291ms 2 NS 0 A 0 MX Secure
2026-11-12 14:48:17 285ms 2 NS 0 A 0 MX Secure
2026-11-11 09:30:18 286ms 2 NS 0 A 0 MX Secure
2026-11-10 03:19:05 316ms 2 NS 0 A 0 MX Secure
2026-11-09 01:41:33 319ms 2 NS 0 A 0 MX Secure
2026-11-08 01:23:02 shown 707ms 2 NS 0 A 0 MX Secure
2026-11-07 00:50:33 330ms 2 NS 0 A 0 MX Secure
2026-10-29 11:50:44 291ms 2 NS 0 A 0 MX Secure
2026-10-09 13:21:38 310ms 2 NS 0 A 0 MX Secure
2026-10-07 09:39:23 320ms 2 NS 0 A 0 MX Secure
2026-09-30 18:44:11 660ms 2 NS 1 A 5 MX Secure
2026-09-26 20:20:21 2701ms 2 NS 1 A 5 MX Secure
2026-09-24 19:56:55 6166ms 2 NS 1 A 5 MX Secure
2026-09-07 22:39:35 771ms 2 NS 1 A 5 MX Secure
2026-08-27 07:34:54 788ms 2 NS 1 A 5 MX Secure
2026-08-26 22:49:10 819ms 2 NS 1 A 5 MX Secure
2026-07-26 17:02:31 1211ms 2 NS 1 A 5 MX Secure
2026-07-10 00:43:18 1410ms 2 NS 1 A 5 MX Secure
2026-07-08 23:58:09 3437ms 2 NS 1 A 5 MX Secure
2026-06-25 20:18:30 813ms 2 NS 1 A 5 MX Secure
2026-06-21 09:56:21 2984ms 2 NS 1 A 5 MX Bogus