bittmann.dk

Historical scan 2026-08-21 20:31:31  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

bittmann.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 1 May 2002 (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   51ms

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 18:04:23
www212.237.249.16 (AS48854) (address records, no CNAME)
www vs bare domainSame network
bittmann.dk: 212.237.249.16 (AS48854)
www.bittmann.dk: 212.237.249.16 (AS48854)
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#

144ms
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: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-01 08:33:05
FieldValue
RegistrarCURANET A/S
Registered2002-05-01
Expires2027-06-30 (222d)

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
51ms
A
70ms
MX
73ms
AAAA
76ms
TXT
315ms
CAA
79ms
HTTPS
73ms
TLSA
24ms
SOA
41ms
MTA-STS
82ms
DNSSEC
144ms
SRV
138ms
Total
874ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-27 18:04:23 568ms 2 NS 1 A 1 MX Secure
2026-10-23 13:25:56 535ms 2 NS 1 A 1 MX Secure
2026-10-22 08:35:28 521ms 2 NS 1 A 1 MX Secure
2026-09-30 21:53:40 1182ms 2 NS 1 A 1 MX Secure
2026-09-25 06:52:56 1163ms 2 NS 1 A 1 MX Secure
2026-09-23 23:08:59 692ms 2 NS 1 A 1 MX Secure
2026-09-17 00:00:47 905ms 2 NS 1 A 1 MX Insecure
2026-09-14 06:10:29 1398ms 2 NS 1 A 1 MX Insecure
2026-08-27 19:50:47 1472ms 2 NS 0 A 0 MX Unknown
2026-08-23 21:55:59 827ms 2 NS 0 A 0 MX Unknown
2026-08-22 20:54:36 4502ms 2 NS 0 A 0 MX Unknown
2026-08-21 20:31:31 shown 874ms 2 NS 0 A 0 MX Unknown
2026-08-20 20:25:32 8713ms 2 NS 0 A 0 MX Unknown
2026-08-19 17:25:27 5875ms 2 NS 0 A 0 MX Unknown
2026-08-18 17:23:03 16730ms 2 NS 0 A 0 MX Unknown
2026-08-17 15:22:51 8711ms 2 NS 0 A 0 MX Unknown
2026-08-15 18:02:18 3080ms 2 NS 0 A 0 MX Unknown
2026-08-14 00:48:56 1438ms 2 NS 0 A 0 MX Unknown
2026-08-12 23:31:25 827ms 2 NS 0 A 0 MX Unknown
2026-08-11 09:44:04 1456ms 2 NS 0 A 0 MX Unknown
2026-08-10 09:32:13 2498ms 2 NS 0 A 0 MX Unknown
2026-08-08 09:29:49 10159ms 2 NS 0 A 0 MX Unknown
2026-08-07 04:32:55 1844ms 2 NS 0 A 0 MX Unknown
2026-08-04 14:31:45 1500ms 2 NS 0 A 0 MX Unknown
2026-07-29 13:59:09 10068ms 2 NS 0 A 0 MX Unknown