broseweddings.dk

📜 Historical scan 2026-06-23 07:51:58 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

broseweddings.dk is a .dk domain served by 3 nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com). It was registered on 6 April 2026 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is DNSSEC-signed and validates, has no DMARC policy and has no IPv6 address. 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#

3 records 64ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.simply.com	2a02:2339:1:15c::4562:4562 91.197.248.78	ns1.simply.com ns1.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.simply.com	185.25.141.15 2a02:2339:4006:101::4562:4562	ns2.simply.com ns2.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns3.simply.com	91.197.248.79	ns3.simply.com	AS48854 team.blue Denmark A/S

🌍 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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-17 00:19:37

www CNAME	broseweddings.netlify.app (all on netlify.app) → 35.157.26.135 63.176.8.218 2a05:d014:58f:6200::258 2a05:d014:58f:6200::259 (AS16509)
www vs bare domain	Same network broseweddings.dk: 75.2.60.5 (AS16509) www.broseweddings.dk: 35.157.26.135 63.176.8.218 2a05:d014:58f:6200::258 2a05:d014:58f:6200::259 (AS16509)
Wildcard	No
Denial of existence	NSEC zone can be walked (all names enumerable)
CDS / CDNSKEY	Published: key rollovers can be automated with the registry (RFC 7344/8078) 1 CDS, 1 CDNSKEY

✍️ DKIM keys#

1 found

Selector	CNAME	Key
google	—	RSA · ~2048 bit

DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

120ms

Check	Result
Validation Status	🔒 Secure
AD Flag (resolver validates)	✓ Set
DS Record	✓ Found
DNSKEY Record	✓ Found
Flags	resolution failed: ncache nxrrset

🏷️ SOA#

29ms

Field	Value
Serial	2026040601
Primary NS (MNAME)	ns1.simply.com
Responsible (RNAME)	hostmaster@simply.com
Refresh	14400s
Retry	3600s
Expire	1209600s
Minimum (neg-cache TTL)	3600s

📋 Registration#

WHOIS fetched 2026-10-04 11:38:32

Field	Value
Registrar	Simply.com A/S
Registered	2026-04-06
Expires	2027-04-05 (163d)

📋 WHOIS#

⏱️ Lookup Timing#

64ms

63ms

99ms

AAAA

62ms

TXT

153ms

CAA

75ms

HTTPS

62ms

TLSA

36ms

SOA

29ms

MTA-STS

74ms

DNSSEC

120ms

SRV

102ms

Total

478ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-17 00:19:37	573ms	3 NS 1 A 1 MX	🔒 Secure
2026-10-12 19:37:40	999ms	3 NS 1 A 1 MX	🔒 Secure
2026-10-07 12:45:01	917ms	3 NS 1 A 1 MX	🔒 Secure
2026-10-04 10:38:27	464ms	3 NS 1 A 1 MX	🔒 Secure
2026-10-03 10:37:27	437ms	3 NS 1 A 1 MX	🔒 Secure
2026-09-02 23:58:29	639ms	3 NS 1 A 1 MX	🔒 Secure
2026-08-05 23:52:22	1010ms	3 NS 1 A 1 MX	🔒 Secure
2026-08-01 03:35:41	17073ms	3 NS 1 A 1 MX	🔒 Secure
2026-07-30 21:45:31	2993ms	3 NS 1 A 1 MX	🔒 Secure
2026-06-30 15:59:08	614ms	3 NS 0 A 0 MX	🔒 Secure
2026-06-26 18:13:38	812ms	3 NS 0 A 0 MX	🔒 Secure
2026-06-23 07:51:58 shown	478ms	3 NS 0 A 0 MX	🔒 Secure
2026-06-16 17:10:36	358ms	3 NS 0 A 0 MX	🔒 Secure