broni.dk

📜 Historical scan 2026-09-18 21:18:52 · ← Latest scan

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

broni.dk is a registered .dk domain whose nameservers (ns5.123hjemmeside.dk, ns6.123hjemmeside.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 5 March 2009 (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 4044ms

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

10078ms

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-16 15:56:18

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2009-03-05
Expires	2027-03-31 (165d)

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

4044ms

4035ms

4030ms

AAAA

4031ms

TXT

20146ms

CAA

4027ms

HTTPS

4027ms

TLSA

4028ms

SOA

4027ms

MTA-STS

4045ms

DNSSEC

10078ms

SRV

4050ms

Total

61289ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 06:37:39	61043ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-18 21:18:52 shown	61289ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 08:14:20	61305ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 22:09:30	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 18:56:26	63383ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 18:32:27	60617ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 18:28:41	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 15:33:15	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 15:27:04	61325ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 17:11:36	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 02:16:05	61383ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 17:19:35	64012ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 16:45:30	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 08:48:08	61277ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 17:15:09	57255ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 13:00:58	61359ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 03:45:40	57633ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 17:10:02	55387ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 10:05:57	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 09:06:33	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 08:05:42	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 07:55:11	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 03:37:47	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 00:17:37	59235ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 15:24:10	65535ms	2 NS 0 A 0 MX	❓ Unknown