haycham.dk

Historical scan 2026-08-19 04:18:59  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

haycham.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 10 January 2014 (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   402ms

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

TLSA / DANE#

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

DNSSEC#

669ms
CheckResult
Validation Status Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates) Not set
DS Record Found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-07 00:11:34
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2014-01-10
Expires2027-01-31 (75d)

Same registrant#

3 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).

DomainRegistrar
alborg9000.dkPunktum dk A/S (direct)
bygningskonsult.dknordicway ApS
reiter.dkPunktum dk A/S (direct)
📋 WHOIS#

Lookup Timing#

NS
402ms
A
381ms
MX
392ms
AAAA
424ms
TXT
1338ms
CAA
374ms
HTTPS
362ms
TLSA
211ms
SOA
288ms
MTA-STS
459ms
DNSSEC
669ms
SRV
441ms
Total
5526ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-22 08:55:00 38847ms 2 NS 0 A 0 MX Unknown
2026-10-07 16:33:34 1296ms 2 NS 0 A 0 MX Bogus
2026-09-26 06:37:11 1353ms 2 NS 0 A 0 MX Bogus
2026-09-09 20:35:20 53413ms 2 NS 0 A 0 MX Unknown
2026-08-28 08:37:14 1446ms 2 NS 0 A 0 MX Bogus
2026-08-23 09:48:46 8954ms 2 NS 0 A 0 MX Bogus
2026-08-22 08:24:27 6573ms 2 NS 0 A 0 MX Bogus
2026-08-21 08:13:03 1083ms 2 NS 0 A 0 MX Bogus
2026-08-20 06:15:22 13060ms 2 NS 0 A 0 MX Bogus
2026-08-19 04:18:59 shown 5526ms 2 NS 0 A 0 MX Bogus
2026-08-17 20:02:21 2703ms 2 NS 0 A 0 MX Bogus
2026-08-16 16:04:44 26634ms 2 NS 0 A 0 MX Unknown
2026-08-15 11:25:58 1515ms 2 NS 0 A 0 MX Bogus
2026-08-14 07:41:36 1010ms 2 NS 0 A 0 MX Bogus
2026-08-12 06:05:20 3461ms 2 NS 0 A 0 MX Bogus
2026-08-07 13:20:38 32097ms 2 NS 0 A 0 MX Unknown
2026-08-06 12:18:11 1430ms 2 NS 0 A 0 MX Bogus
2026-07-31 15:58:36 1390ms 2 NS 0 A 0 MX Bogus
2026-07-27 19:16:26 1350ms 2 NS 0 A 0 MX Bogus
2026-07-26 18:52:33 779ms 2 NS 0 A 0 MX Bogus
2026-07-25 18:30:26 1467ms 2 NS 0 A 0 MX Bogus
2026-07-24 18:03:55 2354ms 2 NS 0 A 0 MX Bogus
2026-07-23 17:18:03 10090ms 2 NS 0 A 0 MX Bogus
2026-07-22 12:36:58 1236ms 2 NS 0 A 0 MX Bogus
2026-07-19 15:58:57 9984ms 2 NS 0 A 0 MX Bogus