fantastic-border.dk

📜 Historical scan 2026-08-10 01:38:28 · ← Latest scan

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

fantastic-border.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 15 January 2008 (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 4080ms

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#

5355ms

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-17 08:15:11

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-01-15
Expires	2027-01-31 (103d)

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

4080ms

4071ms

2122ms

AAAA

4117ms

TXT

16259ms

CAA

2091ms

HTTPS

4089ms

TLSA

2037ms

SOA

55ms

MTA-STS

16077ms

DNSSEC

5355ms

SRV

16092ms

Total

57257ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 10:40:46	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-03 07:58:21	58884ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-27 15:54:25	59139ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 14:08:58	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 13:33:35	65460ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 13:27:12	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 13:13:39	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 09:20:32	61354ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 09:17:36	53923ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 05:17:22	64827ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 05:08:29	63340ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 03:18:35	62163ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 17:07:09	64814ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 04:22:50	60427ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 01:38:28 shown	57257ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 16:06:16	59555ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 21:43:30	63153ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:44:15	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:56:23	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:24:09	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 21:57:48	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 20:33:07	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:14:35	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 19:28:06	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 03:07:20	65535ms	2 NS 0 A 0 MX	❓ Unknown