box4takeaway.dk

📜 Historical scan 2026-08-08 13:19:46 · ← Latest scan

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

box4takeaway.dk is a registered .dk domain whose nameservers (pdns03.domaincontrol.com, pdns04.domaincontrol.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 11 November 2024 (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 992ms

Nameserver	IP addresses	PTR	ASN / ISP
pdns03.domaincontrol.com	2603:5:21f0::33 97.74.111.51	pdns03.domaincontrol.com pdns03.domaincontrol.com	AS44273 Host Europe GmbH AS44273 Host Europe GmbH
pdns04.domaincontrol.com	173.201.79.51 2603:5:22f0::33	pdns04.domaincontrol.com pdns04.domaincontrol.com	AS44273 Host Europe GmbH AS44273 Host Europe GmbH

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

5320ms

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-15 17:34:42

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2024-11-11
Expires	2027-11-10 (378d)

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

992ms

4022ms

6943ms

AAAA

4968ms

TXT

6444ms

CAA

4018ms

HTTPS

5999ms

TLSA

109ms

SOA

38ms

MTA-STS

171ms

DNSSEC

5320ms

SRV

8577ms

Total

11817ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 16:19:52	2947ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 12:18:02	3220ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 06:32:40	10086ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:44:44	7080ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:40:25	5495ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:34:24	7434ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:41:43	2784ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 23:28:09	7537ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 15:43:28	12023ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 12:11:24	5686ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 09:11:12	5065ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 17:22:11	4686ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 23:23:14	3439ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 18:10:04	4235ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 13:19:46 shown	11817ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 12:27:55	3527ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 13:43:44	5021ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 21:44:36	2917ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 21:27:44	1785ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 20:44:09	8406ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 20:26:54	9177ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 20:07:20	16940ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 17:16:36	16908ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 17:43:07	5079ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 09:45:16	11172ms	2 NS 0 A 0 MX	❓ Unknown