pokemonnews.dk

📜 Historical scan 2026-07-03 01:36:18 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Record History ⚡ Scan Now

pokemonnews.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 5 September 2024 (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 87ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com 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

2053ms

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-02 19:56:11

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2024-09-05
Expires	2026-09-04 (expired)

📋 WHOIS

⏱️ Lookup Timing

87ms

94ms

85ms

AAAA

82ms

TXT

406ms

CAA

83ms

HTTPS

83ms

TLSA

80ms

SOA

87ms

MTA-STS

103ms

DNSSEC

2053ms

SRV

89ms

Total

2489ms

🕐 Scan History

Scanned At	Duration	Records	DNSSEC
2026-10-02 19:26:26	184ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-01 19:24:10	249ms	1 NS 0 A 0 MX	❓ Unknown
2026-09-30 19:19:42	715ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-23 21:49:41	55363ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:53:31	5561ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 20:36:09	2949ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 20:23:10	2277ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 18:41:36	30124ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 18:39:47	867ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 10:50:11	4482ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 08:33:48	43596ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 07:59:37	4508ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 10:41:18	1573ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 06:15:08	3335ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 22:37:55	1020ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 23:41:05	29304ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 17:19:40	3527ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:57:25	9201ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:05:34	1360ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:55:28	1404ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 02:30:13	10087ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 02:11:31	9294ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 23:59:37	1215ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 10:48:21	1330ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 08:48:35	1473ms	2 NS 0 A 0 MX	❓ Unknown