gfuhl.dk

📜 Historical scan 2026-08-13 04:31:08 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

gfuhl.dk is a registered .dk domain whose nameservers (ns1.solutio.dk, ns2.solutio.dk, ns3.solutio.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 30 October 2007 (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#

3 records 1034ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.solutio.dk	208.94.148.4	ns10.dnsmadeeasy.com	AS16552 Tiggee LLC
ns2.solutio.dk	208.80.124.4	ns11.dnsmadeeasy.com	AS16552 Tiggee LLC
ns3.solutio.dk	208.80.126.4	ns12.dnsmadeeasy.com	AS16552 Tiggee LLC

🌍 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#

10105ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-13 22:44:06

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2007-10-30
Expires	2026-10-31 (10d)

🔗 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#

1034ms

1007ms

1004ms

AAAA

1028ms

TXT

4946ms

CAA

1007ms

HTTPS

1008ms

TLSA

993ms

SOA

51ms

MTA-STS

1033ms

DNSSEC

10105ms

SRV

1150ms

Total

14997ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 23:40:19	7717ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-24 00:14:11	14476ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-27 22:06:52	9575ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-27 09:37:18	9215ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 02:41:28	1865ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 02:20:22	2131ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 02:11:20	1869ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 00:30:43	2943ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:59:11	18493ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 17:07:06	5766ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 14:13:07	6469ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 04:31:08 shown	14997ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 21:34:02	2233ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 08:19:25	1587ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 20:43:23	1659ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 10:20:45	2095ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-02 06:22:48	14430ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 14:52:27	13941ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:24:34	2379ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:04:09	1600ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:41:53	1630ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:14:48	14108ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 21:37:00	9897ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 17:03:13	2305ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 10:16:59	2270ms	3 NS 0 A 0 MX	❓ Unknown