aaholst.dk

Historical scan 2026-07-25 02:23:13  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

aaholst.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 28 February 2009 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. 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   4139ms

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#

No TXT records found

SPF#

No SPF record — mail spoofing not restricted

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-10-27 21:38:12
www90.184.1.200 (AS203953) (address records, no CNAME)
www vs bare domainSame network
aaholst.dk: 90.184.1.200 (AS203953)
www.aaholst.dk: 90.184.1.200 (AS203953)
WildcardYes: any name under the zone resolves
Denial of existenceNSEC3 · 1 iteration · 1-byte salt RFC 9276 recommends 0 iterations and no salt
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

TLSA / DANE#

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

DNSSEC#

10305ms
CheckResult
Validation Status Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: timed out

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-09 15:01:33
FieldValue
RegistrarDANDOMAIN A/S
Registered2009-02-28
Expires2027-02-28 (102d)

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
4139ms
A
4155ms
MX
4134ms
AAAA
4182ms
TXT
16323ms
CAA
4199ms
HTTPS
4168ms
TLSA
4025ms
SOA
4168ms
MTA-STS
4263ms
DNSSEC
10305ms
SRV
4222ms
Total
49780ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-27 21:38:12 367ms 2 NS 1 A 0 MX Secure
2026-10-25 08:21:19 663ms 2 NS 1 A 0 MX Secure
2026-10-22 02:44:24 465ms 2 NS 1 A 0 MX Secure
2026-10-13 05:27:30 1161ms 2 NS 1 A 0 MX Secure
2026-10-03 15:22:52 356ms 2 NS 1 A 0 MX Insecure
2026-09-25 08:37:24 418ms 2 NS 1 A 0 MX Insecure
2026-09-24 01:41:24 702ms 2 NS 1 A 0 MX Insecure
2026-09-08 17:23:37 3408ms 2 NS 0 A 0 MX Unknown
2026-08-23 17:43:41 3243ms 2 NS 0 A 0 MX Unknown
2026-08-22 17:28:48 1866ms 2 NS 0 A 0 MX Unknown
2026-08-21 17:17:34 7101ms 2 NS 0 A 0 MX Unknown
2026-08-20 17:14:25 4372ms 2 NS 0 A 0 MX Unknown
2026-08-19 14:26:25 2307ms 2 NS 0 A 0 MX Unknown
2026-08-18 14:25:41 26096ms 2 NS 0 A 0 MX Unknown
2026-08-17 10:36:50 941ms 2 NS 0 A 0 MX Unknown
2026-08-15 16:24:16 3275ms 2 NS 0 A 0 MX Unknown
2026-08-14 13:48:14 10219ms 2 NS 0 A 0 MX Unknown
2026-08-13 11:12:46 2940ms 2 NS 0 A 0 MX Unknown
2026-08-11 15:29:06 21883ms 2 NS 0 A 0 MX Unknown
2026-08-09 23:15:37 2972ms 2 NS 0 A 0 MX Unknown
2026-08-03 18:49:48 1401ms 2 NS 0 A 0 MX Unknown
2026-07-30 20:07:31 1084ms 2 NS 0 A 0 MX Unknown
2026-07-29 11:55:33 10082ms 2 NS 0 A 0 MX Unknown
2026-07-28 04:49:32 2862ms 2 NS 0 A 0 MX Unknown
2026-07-27 03:37:55 2870ms 2 NS 0 A 0 MX Unknown