afap.dk

📜 Historical scan 2026-07-28 05:38:30 · ← Latest scan

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

afap.dk is a registered .dk domain whose nameservers (ns17.bitpalast.net, ns29.bitpalast.net, ns37.bitpalast.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 19 March 2019 (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 2019ms

Nameserver	IP addresses	PTR	ASN / ISP
ns17.bitpalast.net	87.238.196.5	ns1.start-dns.de	AS42730 EVANZO e-commerce GmbH
ns29.bitpalast.net	178.254.5.5	ns2.start-dns.de	AS42730 EVANZO e-commerce GmbH
ns37.bitpalast.net	178.254.63.7	ns3.start-dns.de	AS8893 Artfiles New Media 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#

9064ms

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 23:53:50

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2019-03-19
Expires	2027-03-31 (164d)

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

2019ms

4029ms

2029ms

AAAA

4028ms

TXT

7341ms

CAA

4028ms

HTTPS

4026ms

TLSA

429ms

SOA

23ms

MTA-STS

4039ms

DNSSEC

9064ms

SRV

4030ms

Total

12137ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-29 18:44:53	5826ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-26 22:03:30	6359ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 18:01:01	2939ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 17:34:45	12411ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:28:07	3596ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 17:18:18	6631ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:56:40	17555ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 03:03:34	7984ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 19:59:50	12120ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 16:53:11	11991ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 02:50:49	1878ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 00:31:26	7001ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 05:43:15	9100ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 01:56:59	14462ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-02 22:27:49	3155ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 05:38:30 shown	12137ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 05:10:14	12007ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 04:44:15	2358ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 04:07:01	2141ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 03:10:44	2171ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 01:30:38	10524ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 22:30:35	12248ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 21:21:56	12151ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 18:49:50	11833ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 16:43:36	7923ms	3 NS 0 A 0 MX	❓ Unknown