dankinkbh.dk

📜 Historical scan 2026-08-12 10:24:08 · ← Latest scan

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

dankinkbh.dk is a registered .dk domain whose nameservers (ns5.123hjemmeside.dk, ns6.123hjemmeside.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 4 March 2009 (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 4033ms

Nameserver	IP addresses	PTR	ASN / ISP
ns5.123hjemmeside.dk	52.200.246.146	ec2-52-200-246-146.compute-1.amazonaws.com	AS14618 Amazon.com, Inc.
ns6.123hjemmeside.dk	52.51.2.215	ec2-52-51-2-215.eu-west-1.compute.amazonaws.com	AS16509 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#

10094ms

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-17 18:38:47

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2009-03-04
Expires	2027-03-31 (163d)

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

4033ms

4045ms

4049ms

AAAA

4070ms

TXT

20180ms

CAA

4049ms

HTTPS

4054ms

TLSA

4029ms

SOA

4058ms

MTA-STS

4051ms

DNSSEC

10094ms

SRV

4070ms

Total

65402ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-02 05:23:21	63809ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 22:15:04	61510ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 22:00:36	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 21:46:06	59619ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 21:43:29	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 20:54:14	61455ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 20:42:19	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 12:55:05	63377ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 12:14:11	61305ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 11:57:28	59221ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 10:24:08 shown	65402ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 22:51:46	59119ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 19:47:03	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 22:19:14	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 17:06:53	61202ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:32:20	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:46:27	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 23:15:03	63272ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:37:09	61246ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 21:35:43	59228ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:35:35	64518ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 23:52:34	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 20:49:08	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 18:46:41	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-16 06:10:56	59204ms	2 NS 0 A 0 MX	❓ Unknown