bumbleandbumble.dk

📜 Historical scan 2026-07-18 03:31:02 · ← Latest scan

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

bumbleandbumble.dk is a registered .dk domain whose nameservers (ns2.elcompanies.com, ns4.elcompanies.com, ns5.elcompanies.com) 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#

3 records 179ms

Nameserver	IP addresses	PTR	ASN / ISP
ns2.elcompanies.com	173.245.58.41 2400:cb00:2049:1::adf5:3a29	— —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns4.elcompanies.com	162.159.8.101 2400:cb00:2049:1::a29f:865	— —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns5.elcompanies.com	162.159.9.165 2400:cb00:2049:1::a29f:9a5	— —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, 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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-09 16:33:42

www	NXDOMAIN
www vs bare domain	Neither resolves bumbleandbumble.dk: no address www.bumbleandbumble.dk: no address
Wildcard	No

🔗 TLSA / DANE#

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

🔐 DNSSEC#

2212ms

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#

179ms

176ms

179ms

AAAA

175ms

TXT

889ms

CAA

174ms

HTTPS

177ms

TLSA

312ms

SOA

178ms

MTA-STS

189ms

DNSSEC

2212ms

SRV

185ms

Total

3670ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-27 07:36:34	617ms	4 NS 0 A 0 MX	🔓 Insecure
2026-08-15 10:59:11	719ms	4 NS 0 A 0 MX	🔓 Insecure
2026-08-13 10:00:42	16824ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 13:55:47	1763ms	4 NS 0 A 0 MX	🔓 Insecure
2026-08-10 04:09:26	3375ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 03:19:17	16939ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 18:41:30	16795ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-30 18:43:52	2047ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 03:12:41	2375ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 22:53:43	16861ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:35:54	2476ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:15:49	1636ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:00:21	3620ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 19:19:00	10523ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 17:58:55	10520ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 13:13:50	17045ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 10:28:12	25714ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 06:06:00	19109ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 03:31:02 shown	3670ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-17 01:03:50	19009ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-15 03:35:43	3444ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-08 19:09:27	5900ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-07 07:29:57	4126ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-06 01:06:05	2310ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-04 22:14:19	4795ms	3 NS 0 A 0 MX	❓ Unknown