geth.dk

📜 Historical scan 2026-08-21 02:08:37 · ← Latest scan

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

geth.dk is a registered .dk domain whose nameservers (ns1.123hjemmeside.dk, ns2.123hjemmeside.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 3 September 2010 (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 16058ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.123hjemmeside.dk	52.51.2.215	ec2-52-51-2-215.eu-west-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.
ns2.123hjemmeside.dk	52.200.246.146	ec2-52-200-246-146.compute-1.amazonaws.com	AS14618 Amazon.com, Inc.

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

16145ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-16 19:02:21

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2010-09-03
Expires	2027-09-30 (348d)

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

16058ms

3053ms

16067ms

AAAA

16055ms

TXT

46211ms

CAA

16094ms

HTTPS

11091ms

TLSA

2082ms

SOA

56ms

MTA-STS

10146ms

DNSSEC

16145ms

SRV

16067ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 01:54:14	61034ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-02 22:19:28	56902ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 14:14:38	59376ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 06:10:16	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 02:46:55	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 02:20:13	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 02:08:37 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 00:56:58	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:56:09	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 09:12:19	59252ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 20:29:49	61756ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 13:09:02	59616ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 17:10:35	59210ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 18:51:48	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 11:48:22	63408ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 16:10:10	64903ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 09:50:34	65225ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 08:32:54	61179ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 08:18:31	59198ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 08:15:26	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 07:07:31	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 06:32:26	61225ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 04:25:57	61225ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 02:51:32	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 01:16:13	62111ms	2 NS 0 A 0 MX	❓ Unknown