megapari.dk

📜 Historical scan 2026-07-24 17:10:24 · ← Latest scan

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

megapari.dk is a registered .dk domain whose nameservers (eu.atakdomain.com, tr.atakdomain.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 15 May 2023 (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 838ms

Nameserver	IP addresses	PTR	ASN / ISP
eu.atakdomain.com	168.119.233.136 51.75.28.75	static.136.233.119.168.clients.your-server.de 75.ip-51-75-28.eu	AS24940 Hetzner Online GmbH AS16276 OVH SAS
tr.atakdomain.com	185.46.40.60	—	AS211401 Atak Domain Bilgi Teknolojileri A.S.

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

9883ms

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 10:36:15

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2023-05-15
Expires	2027-05-14 (206d)

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

838ms

819ms

831ms

AAAA

836ms

TXT

4208ms

CAA

832ms

HTTPS

835ms

TLSA

826ms

SOA

16ms

MTA-STS

824ms

DNSSEC

9883ms

SRV

911ms

Total

13515ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-29 15:32:48	8122ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-25 00:36:21	7193ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 01:06:23	8093ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 11:45:20	3709ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:52:59	19590ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 10:30:31	7184ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:24:14	7215ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:40:39	12414ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 05:49:57	11298ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 05:26:24	8542ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 02:09:54	7141ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 11:32:24	6885ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 22:37:51	13351ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 09:28:49	8989ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 08:35:42	13430ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 18:36:29	2080ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 00:28:21	8127ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:53:32	13210ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:55:14	10175ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:36:34	9563ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:10:24 shown	13515ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:48:49	13481ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:35:41	2187ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 06:13:40	2319ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 20:35:55	2074ms	2 NS 0 A 0 MX	❓ Unknown