parmaparmesan.dk

📜 Historical scan 2026-08-08 22:38:42 · ← Latest scan

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

parmaparmesan.dk is a registered .dk domain whose nameservers (ns.abdns.biz, ns.abdns.eu, ns.abdns.info) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 15 September 2017 (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#

3 records 1402ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.abdns.biz	95.110.136.38	ns.abdns.biz	AS31034 Aruba S.p.A.
ns.abdns.eu	31.14.130.20	ns.abdns.eu	AS31034 Aruba S.p.A.
ns.abdns.info	217.61.96.167	ns.abdns.info	AS199653 Aruba S.p.A.

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

1836ms

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-14 16:29:26

Field	Value
Registrar	Ovh
Registered	2017-09-15
Expires	2027-09-30 (341d)

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

1402ms

1754ms

1440ms

AAAA

1458ms

TXT

4860ms

CAA

1702ms

HTTPS

1757ms

TLSA

766ms

SOA

38ms

MTA-STS

1428ms

DNSSEC

1836ms

SRV

1684ms

Total

8896ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-22 13:33:05	7698ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-01 23:16:10	14253ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-26 20:33:22	7767ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 14:15:08	14125ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 12:55:52	3442ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 12:52:23	8384ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:06:36	11243ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:30:11	5676ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 07:24:22	14280ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 08:32:52	14152ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 02:31:14	19294ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 20:08:11	11149ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 11:57:05	10608ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 09:34:58	9941ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 00:24:52	7729ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 22:38:42 shown	8896ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 20:34:10	8892ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 18:13:13	6432ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:11:57	18089ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 16:43:02	2849ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 16:14:53	7557ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 16:05:53	10580ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:57:14	3319ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 06:15:24	2923ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 05:11:05	9655ms	3 NS 0 A 0 MX	❓ Unknown