gardoe.dk

Historical scan 2026-10-20 13:28:43  ·  ← Latest scan
Zone File Timeline & History Scan Now

gardoe.dk is a .dk domain served by 2 nameservers (ns01.one.com, ns02.one.com). It was registered on 20 March 2001 (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   114ms

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   322ms
TXT Record
v=spf1 -all

SPF#

PolicyRecord (gardoe.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-06 22:15:37
wwwNXDOMAIN
www vs bare domainNeither resolves
gardoe.dk: no address
www.gardoe.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#

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

SOA#

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

Registration#

WHOIS fetched 2026-11-07 12:48:57
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2001-03-20
Expires2027-03-31 (132d)

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
114ms
A
118ms
MX
63ms
AAAA
115ms
TXT
322ms
CAA
91ms
HTTPS
127ms
TLSA
49ms
SOA
64ms
MTA-STS
148ms
DNSSEC
324ms
SRV
150ms
Total
842ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-07 22:19:51 1806ms 2 NS 0 A 0 MX Bogus
2026-11-06 22:15:36 312ms 2 NS 0 A 0 MX Secure
2026-11-05 22:14:28 314ms 2 NS 0 A 0 MX Secure
2026-11-04 21:56:42 366ms 2 NS 0 A 0 MX Secure
2026-11-03 21:50:44 397ms 2 NS 0 A 0 MX Secure
2026-11-02 15:06:22 293ms 2 NS 0 A 0 MX Secure
2026-11-01 06:25:23 294ms 2 NS 0 A 0 MX Secure
2026-10-29 12:14:38 2224ms 2 NS 0 A 0 MX Secure
2026-10-27 03:00:41 742ms 2 NS 0 A 0 MX Secure
2026-10-24 13:16:40 866ms 2 NS 0 A 0 MX Secure
2026-10-23 08:30:34 926ms 2 NS 0 A 0 MX Secure
2026-10-21 20:22:47 880ms 2 NS 0 A 0 MX Secure
2026-10-20 13:28:43 shown 842ms 2 NS 0 A 0 MX Secure
2026-10-07 09:59:13 449ms 2 NS 0 A 0 MX Secure
2026-09-28 02:06:33 620ms 2 NS 1 A 4 MX Secure
2026-09-23 18:29:39 749ms 2 NS 1 A 4 MX Secure
2026-09-11 10:03:36 686ms 2 NS 1 A 4 MX Secure
2026-08-21 23:47:14 1465ms 2 NS 1 A 4 MX Secure
2026-08-20 23:24:10 2340ms 2 NS 1 A 4 MX Secure
2026-07-22 16:37:39 1038ms 2 NS 1 A 4 MX Secure
2026-07-02 03:23:25 895ms 2 NS 1 A 4 MX Secure
2026-06-24 15:25:35 1036ms 2 NS 1 A 4 MX Secure
2026-06-20 10:16:30 575ms 2 NS 1 A 4 MX Secure
2026-06-17 09:18:53 1437ms 2 NS 1 A 4 MX Secure