bredsten-kattepension.dk

📜 Historical scan 2026-07-23 20:53:36 · ← Latest scan

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

bredsten-kattepension.dk is a registered .dk domain whose nameservers (ns1.register.it, ns2.register.it) do not answer for it, so it is currently a lame delegation and does not resolve. It 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 122ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.register.it	2a01:8100:2911::2:184:2 81.88.61.2	— host-81-88-61-2.dedicatedservers.it	AS39729 Register S.p.A. AS39729 Register S.p.A.
ns2.register.it	195.7.227.1 2a00:13b0:2::227:1	ns2.register.it —	AS8622 Team Blue Internet Services Uk Limited AS8622 Team Blue Internet Services Uk Limited

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

187ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

122ms

117ms

111ms

AAAA

123ms

TXT

864ms

CAA

119ms

HTTPS

119ms

TLSA

107ms

SOA

28ms

MTA-STS

719ms

DNSSEC

187ms

SRV

859ms

Total

1938ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 17:56:08	9753ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 04:46:05	5487ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 04:22:48	17554ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 04:07:05	8259ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 03:53:50	4851ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 03:07:20	2409ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:11:19	5277ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 22:15:08	11183ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 14:13:43	7390ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 03:08:45	5095ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 21:13:10	17597ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 18:06:42	2067ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 10:51:12	10116ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 16:58:05	6319ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:18:41	4909ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 01:27:14	9731ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 01:03:43	1959ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 00:48:20	12673ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 20:53:36 shown	1938ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 19:36:58	4838ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 02:48:47	4794ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 20:22:15	9065ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 18:01:30	2047ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 15:38:11	9229ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-12 07:52:25	2161ms	2 NS 0 A 0 MX	❓ Unknown