wildlife.dk

📜 Historical scan 2026-08-22 03:41:21 · ← Latest scan

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

wildlife.dk is a registered .dk domain whose nameservers (ns.scannet2.dk, ns2.scannet2.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 7 May 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 97ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.scannet2.dk	185.25.141.9 2a02:2339:4006:10d::4171:4171	ns1.scannet.dk ns1.scannet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.scannet2.dk	2a02:2339:1:112:0:5:1:b11 91.197.248.72	ns2.scannet.dk ns2.scannet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark 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#

9132ms

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-25 05:16:45

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	1998-05-07
Expires	2027-06-30 (248d)

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

97ms

95ms

104ms

AAAA

95ms

TXT

353ms

CAA

94ms

HTTPS

89ms

TLSA

68ms

SOA

44ms

MTA-STS

107ms

DNSSEC

9132ms

SRV

106ms

Total

11111ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 22:06:33	787ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-03 23:28:44	2653ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 03:52:40	5721ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 03:41:21 shown	11111ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 03:28:03	10140ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:19:28	2918ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 23:45:00	10058ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 07:47:16	3642ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 00:23:10	892ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 23:40:04	2893ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 18:03:42	2845ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 08:43:14	1086ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 22:22:02	9415ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 14:26:06	2874ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 22:45:56	988ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:05:46	16738ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 21:52:43	1032ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 21:44:28	9904ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:28:56	9836ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 16:01:19	1608ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 09:19:05	16822ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 05:29:47	1060ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 23:04:12	936ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 22:41:13	2883ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 04:29:39	997ms	2 NS 0 A 0 MX	❓ Unknown