gaflen.dk

Historical scan 2026-06-17 09:29:45  ·  ← Latest scan
Zone File Timeline & History Scan Now
This domain left the .dk zone on 2026-10-02 (it is no longer in the registry's zone list). The records below are from our last scan before that.

gaflen.dk is a .dk domain served by 4 nameservers (ns1-08.azure-dns.com, ns2-08.azure-dns.net, ns3-08.azure-dns.org and 1 more). It was already in the .dk zone when our tracking began on 16 June 2026. Its website address 195.41.97.145 is hosted by TDC Holding A/S (AS3292) in Denmark. Mail is handled by mail2.nordjyske.dk, mail4.nordjyske.dk. The zone is not DNSSEC-signed, 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#

4 records   66ms
NameserverIP addressesPTRASN / ISP
ns1-08.azure-dns.com — — —
ns2-08.azure-dns.net — — —
ns3-08.azure-dns.org — — —
ns4-08.azure-dns.info — — —

A Records#

1 records   63ms
IPTTLPTRASNISP / OrgCIDRCountryCity
195.41.97.145 — — AS3292 TDC Holding A/S 195.41.0.0/16 🇩🇰 Denmark Copenhagen

MX Records#

2 records   61ms

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#

168ms
CheckResult
Validation Status Insecure
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsunsigned answer

SOA#

53ms
FieldValue
Serial2004031216
Primary NS (MNAME)ns1-08.azure-dns.com
Responsible (RNAME)postmaster@ammulti.dk
Refresh10800s
Retry1800s
Expire3600000s
Minimum (neg-cache TTL)3600s

Registration#

No registration data yet — queued for a WHOIS lookup
📋 WHOIS#

Lookup Timing#

NS
66ms
A
63ms
MX
61ms
AAAA
54ms
TXT
147ms
CAA
48ms
HTTPS
68ms
TLSA
175ms
SOA
53ms
MTA-STS
56ms
DNSSEC
168ms
SRV
0ms
Total
692ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-08-23 17:36:04 11079ms 4 NS 0 A 0 MX Unknown
2026-08-22 15:39:10 2168ms 4 NS 0 A 0 MX Unknown
2026-08-21 15:12:26 2499ms 4 NS 0 A 0 MX Unknown
2026-08-20 14:58:21 12057ms 4 NS 0 A 0 MX Unknown
2026-08-19 04:21:26 4259ms 4 NS 0 A 0 MX Unknown
2026-08-17 19:48:37 9475ms 4 NS 0 A 0 MX Unknown
2026-08-15 10:26:29 4232ms 4 NS 0 A 0 MX Unknown
2026-08-12 06:17:55 3199ms 4 NS 0 A 0 MX Unknown
2026-08-10 21:42:01 5074ms 4 NS 0 A 0 MX Unknown
2026-08-09 19:13:29 2932ms 4 NS 0 A 0 MX Unknown
2026-08-08 17:14:54 4005ms 4 NS 0 A 0 MX Unknown
2026-08-06 00:42:15 2818ms 4 NS 0 A 0 MX Unknown
2026-08-01 21:36:45 3980ms 4 NS 0 A 0 MX Unknown
2026-07-28 06:08:07 4219ms 4 NS 0 A 0 MX Unknown
2026-07-27 05:16:34 1536ms 4 NS 0 A 0 MX Unknown
2026-07-26 04:43:19 1836ms 4 NS 0 A 0 MX Unknown
2026-07-25 04:19:12 1559ms 4 NS 0 A 0 MX Unknown
2026-07-24 03:13:48 9333ms 4 NS 0 A 0 MX Unknown
2026-07-23 02:24:49 1822ms 4 NS 0 A 0 MX Unknown
2026-07-21 23:27:05 3946ms 4 NS 0 A 0 MX Unknown
2026-07-20 18:01:57 1900ms 4 NS 0 A 0 MX Unknown
2026-07-19 00:02:32 1645ms 4 NS 0 A 0 MX Unknown
2026-07-17 21:48:12 7925ms 4 NS 0 A 0 MX Unknown
2026-07-15 21:54:16 2283ms 4 NS 0 A 0 MX Unknown
2026-07-13 20:24:29 2761ms 4 NS 0 A 0 MX Unknown