calmar.dk

📜 Historical scan 2026-08-15 13:36:37 · ← Latest scan

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

calmar.dk is a registered .dk domain whose nameservers (ns1.euro909.com, ns3.euro909.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 3 July 1998 (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 93ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.euro909.com	156.154.130.100 2610:a1:1022::100	indom30.indomco.fr ns.domainnetwork.se	AS12008 Vercara, LLC AS12008 Vercara, LLC
ns3.euro909.com	156.154.131.100 2610:a1:1023::100	ns2.arcemus.com indom80.indomco.hk	AS12008 Vercara, LLC AS12008 Vercara, LLC

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

149ms

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-23 11:21:53

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	1998-07-03
Expires	2027-09-30 (340d)

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

93ms

79ms

91ms

AAAA

82ms

TXT

584ms

CAA

91ms

HTTPS

80ms

TLSA

92ms

SOA

39ms

MTA-STS

103ms

DNSSEC

149ms

SRV

8235ms

Total

9230ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 07:48:58	2995ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-03 17:13:26	2802ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 20:43:53	4244ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:32:36	3210ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 20:27:12	4911ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 20:17:50	2199ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 18:22:28	7352ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 18:19:56	5350ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 14:57:37	2873ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 13:36:37 shown	9230ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 10:51:56	3581ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 18:26:35	2888ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 15:13:03	3694ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 14:29:49	2904ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 00:41:04	11199ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 21:24:38	1247ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 03:58:27	10999ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 11:38:51	3337ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 10:59:31	9304ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 10:32:38	1468ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 10:14:26	1367ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 09:12:05	1457ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 19:34:33	10845ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 17:37:35	1285ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 21:07:02	1503ms	2 NS 0 A 0 MX	❓ Unknown