bryllupsbladet.dk

📜 Historical scan 2026-08-13 08:51:02 · ← Latest scan

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

bryllupsbladet.dk is a registered .dk domain whose nameservers (ns1.aspectnetworks.dk, ns2.aspectnetworks.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 5 April 2001 (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 4357ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.aspectnetworks.dk	185.51.79.31	a400backup.powernet.dk	AS205984 Powernet Aps
ns2.aspectnetworks.dk	185.51.79.31	a400backup.powernet.dk	AS205984 Powernet Aps

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

10542ms

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-13 21:38:01

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2001-04-05
Expires	2027-06-30 (254d)

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

4357ms

4330ms

4316ms

AAAA

4342ms

TXT

12797ms

CAA

4342ms

HTTPS

4305ms

TLSA

2070ms

SOA

4333ms

MTA-STS

4367ms

DNSSEC

10542ms

SRV

4388ms

Total

58243ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-27 06:52:29	55397ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 22:43:41	64315ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 19:52:31	60395ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 19:32:15	57165ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 19:27:49	54499ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 19:04:18	59696ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 19:01:16	54866ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 13:38:49	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 19:30:01	54484ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 15:10:01	55553ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 08:51:02 shown	58243ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 08:14:45	57334ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 03:45:48	55378ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 22:03:22	55107ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 03:46:42	61226ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 21:49:53	59260ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 10:34:36	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 23:40:56	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 21:03:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 19:37:09	59187ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:06:30	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:46:37	53253ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:16:20	57246ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 16:51:41	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:09:35	52774ms	2 NS 0 A 0 MX	❓ Unknown