takeaway-odense.dk

📜 Historical scan 2026-08-20 12:27:14 · ← Latest scan

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

takeaway-odense.dk is a registered .dk domain whose nameservers (dns1.vps.net, dns2.vps.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 19 July 2011 (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 593ms

Nameserver	IP addresses	PTR	ASN / ISP
dns1.vps.net	67.228.254.4	4.fe.e443.ip4.static.sl-reverse.com	AS36351 IBM Cloud
dns2.vps.net	2607:f0d0:0:f:2::1 67.228.255.5	ns2.softlayer.com 5.ff.e443.ip4.static.sl-reverse.com	AS36351 IBM Cloud AS36351 IBM Cloud

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

734ms

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-20 19:47:59

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-07-19
Expires	2027-07-31 (281d)

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

593ms

587ms

615ms

AAAA

591ms

TXT

1925ms

CAA

605ms

HTTPS

563ms

TLSA

332ms

SOA

337ms

MTA-STS

615ms

DNSSEC

734ms

SRV

595ms

Total

6089ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 20:41:13	3707ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 03:00:09	4143ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-18 16:33:08	11344ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-02 13:15:46	12372ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 10:34:25	2874ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 13:35:58	5277ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 13:09:23	3379ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 13:00:17	2449ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:27:14 shown	6089ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:32:23	18704ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 07:00:41	3009ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 19:58:12	4938ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 17:11:02	3397ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 00:40:05	3157ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 00:15:54	11413ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 19:15:33	6078ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 10:18:19	2528ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 08:04:02	2677ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 21:49:05	11353ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 16:07:49	4432ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 11:25:12	11487ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:18:59	3069ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:10:25	3767ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:36:40	5704ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:14:35	17662ms	2 NS 0 A 0 MX	❓ Unknown