jack-russel.dk

📜 Historical scan 2026-07-24 12:08:53 · ← Latest scan

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

jack-russel.dk is a registered .dk domain whose nameservers (ns1.ppi.dk, ns2.ppi.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 3 June 2004 (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 119ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.ppi.dk	52.30.62.50	ec2-52-30-62-50.eu-west-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.
ns2.ppi.dk	35.156.158.113	ec2-35-156-158-113.eu-central-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.

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

197ms

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-21 04:59:41

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-06-03
Expires	2027-06-30 (246d)

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

119ms

116ms

119ms

AAAA

115ms

TXT

663ms

CAA

109ms

HTTPS

112ms

TLSA

8099ms

SOA

35ms

MTA-STS

118ms

DNSSEC

197ms

SRV

449ms

Total

10340ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-27 20:45:51	4126ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 14:59:21	5810ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 11:26:40	2489ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 11:20:34	12138ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 10:59:11	9710ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 08:09:30	4652ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 08:00:41	4214ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 20:13:35	4923ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 16:11:27	11818ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 11:11:12	7419ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 20:42:18	2073ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 21:18:03	4626ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 05:09:47	11778ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 04:50:02	6238ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 14:06:11	4928ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:35:56	9609ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 13:13:22	2185ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:28:31	4116ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 12:08:53 shown	10340ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:21:14	4563ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 05:46:15	2217ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 01:32:27	1636ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 10:14:19	4016ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 05:00:52	6568ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 01:49:16	17688ms	2 NS 0 A 0 MX	❓ Unknown