bidzup.dk

📜 Historical scan 2026-07-21 17:39:51 · ← Latest scan

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

bidzup.dk is a registered .dk domain whose nameservers (ns1.inleed.net, ns2.inleed.net, ns3.inleed.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 24 November 2025 (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#

3 records 349ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.inleed.net	185.189.49.214 2001:67c:750::2	ns1.inleed.net ns1.inleed.net	AS206170 Yelles AB AS206170 Yelles AB
ns2.inleed.net	185.189.49.215 2001:67c:750::3	ns2.inleed.net ns2.inleed.net	AS206170 Yelles AB AS206170 Yelles AB
ns3.inleed.net	185.189.49.216	ns3.inleed.net	AS206170 Yelles AB

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

383ms

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#

WHOIS fetched 2026-10-13 23:46:38

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2025-11-24
Expires	2026-11-23 (33d)

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

349ms

350ms

AAAA

347ms

TXT

1737ms

CAA

346ms

HTTPS

346ms

TLSA

349ms

SOA

350ms

MTA-STS

355ms

DNSSEC

383ms

SRV

351ms

Total

3717ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 12:54:11	10125ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:34:27	9448ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:25:11	13698ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 07:32:23	18341ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:21:43	15505ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 04:54:04	1365ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 15:03:51	8988ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 23:29:08	1247ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 16:30:38	16929ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:14:55	12510ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 01:20:37	7951ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 02:48:51	12641ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 14:10:44	13459ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 08:20:06	11510ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 08:00:09	1714ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 07:50:42	1396ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 06:27:45	1451ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 06:10:59	4106ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 17:39:51 shown	3717ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 16:14:00	15819ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 13:04:25	11347ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 11:28:28	11476ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-17 06:33:34	4529ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-15 12:06:33	11274ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-12 01:27:04	1420ms	3 NS 0 A 0 MX	❓ Unknown