gulddal.dk

Historical scan 2026-08-22 02:24:06  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

gulddal.dk is a registered .dk domain whose nameservers (ns.locuples.com, ns2.locuples.com, ns3.wwi.as and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 13 January 2005 (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#

4 records   821ms

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#

1016ms
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-13 13:16:40
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2005-01-13
Expires2027-01-31 (74d)

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
821ms
A
823ms
MX
771ms
AAAA
815ms
TXT
3215ms
CAA
802ms
HTTPS
813ms
TLSA
639ms
SOA
289ms
MTA-STS
717ms
DNSSEC
1016ms
SRV
825ms
Total
9202ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-08-26 19:02:12 14444ms 4 NS 0 A 0 MX Unknown
2026-08-24 07:01:52 9425ms 4 NS 0 A 0 MX Unknown
2026-08-23 02:52:28 2157ms 4 NS 0 A 0 MX Unknown
2026-08-22 02:24:06 shown 9202ms 4 NS 0 A 0 MX Unknown
2026-08-21 02:21:33 9308ms 4 NS 0 A 0 MX Unknown
2026-08-20 01:54:58 3737ms 4 NS 0 A 0 MX Unknown
2026-08-18 23:49:55 5289ms 4 NS 0 A 0 MX Unknown
2026-08-17 06:55:28 5109ms 4 NS 0 A 0 MX Unknown
2026-08-13 19:40:33 8723ms 4 NS 0 A 0 MX Unknown
2026-08-12 11:12:09 8798ms 4 NS 0 A 0 MX Unknown
2026-08-10 07:21:42 7149ms 4 NS 0 A 0 MX Unknown
2026-08-06 16:49:46 14576ms 4 NS 0 A 0 MX Unknown
2026-07-27 22:23:54 9392ms 4 NS 0 A 0 MX Unknown
2026-07-26 21:33:50 14989ms 4 NS 0 A 0 MX Unknown
2026-07-25 21:08:01 9482ms 4 NS 0 A 0 MX Unknown
2026-07-24 20:39:44 9620ms 4 NS 0 A 0 MX Unknown
2026-07-23 19:27:10 13932ms 4 NS 0 A 0 MX Unknown
2026-07-22 18:07:15 2150ms 4 NS 0 A 0 MX Unknown
2026-07-21 17:16:55 9668ms 4 NS 0 A 0 MX Unknown
2026-07-20 03:56:00 9855ms 4 NS 0 A 0 MX Unknown
2026-07-18 22:18:18 1763ms 4 NS 0 A 0 MX Unknown
2026-07-17 21:09:19 17449ms 4 NS 0 A 0 MX Unknown
2026-07-16 01:41:27 1925ms 4 NS 0 A 0 MX Unknown
2026-07-12 13:14:07 9829ms 4 NS 0 A 0 MX Unknown
2026-07-11 10:11:37 2087ms 4 NS 0 A 0 MX Unknown