kennelbradfield.dk

📜 Historical scan 2026-08-21 15:11:29 · ← Latest scan

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

kennelbradfield.dk is a registered .dk domain whose nameservers (ns4.123hjemmeside.dk, ns5.123hjemmeside.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 1 December 2008 (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 8078ms

Nameserver	IP addresses	PTR	ASN / ISP
ns4.123hjemmeside.dk	52.51.2.215	ec2-52-51-2-215.eu-west-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.
ns5.123hjemmeside.dk	52.200.246.146	ec2-52-200-246-146.compute-1.amazonaws.com	AS14618 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#

16094ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-20 17:43:23

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-12-01
Expires	2026-12-31 (70d)

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

8078ms

3062ms

8057ms

AAAA

3070ms

TXT

62180ms

CAA

3067ms

HTTPS

3063ms

TLSA

2108ms

SOA

3068ms

MTA-STS

16060ms

DNSSEC

16094ms

SRV

16075ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-27 23:41:52	57115ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 04:50:16	57470ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 16:42:02	63442ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 15:43:53	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 15:11:29 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:04:57	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:12:31	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 06:43:10	59070ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 01:34:23	57875ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 21:53:55	62496ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 14:01:05	61566ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 08:01:56	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 07:15:40	59699ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 05:56:49	56628ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 16:49:41	60544ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 03:53:27	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 05:09:30	59300ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 17:42:33	62432ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 15:28:47	63370ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 15:05:20	59249ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:49:02	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:19:51	63165ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 12:50:52	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 00:54:32	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 22:14:09	65535ms	2 NS 0 A 0 MX	❓ Unknown