wedodeli.dk

📜 Historical scan 2026-08-14 09:32:01 · ← Latest scan

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

wedodeli.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 October 2007 (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 365ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com 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

🔗 TLSA / DANE#

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

🔐 DNSSEC#

558ms

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-18 11:48:21

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2007-10-02
Expires	2027-10-31 (370d)

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

365ms

369ms

329ms

AAAA

373ms

TXT

1253ms

CAA

359ms

HTTPS

359ms

TLSA

351ms

SOA

275ms

MTA-STS

402ms

DNSSEC

558ms

SRV

437ms

Total

4372ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 20:19:08	1374ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-02 14:48:04	4449ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 02:51:23	3931ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 23:22:38	1602ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 23:11:36	7046ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 23:07:02	1483ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 22:37:39	27167ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:12:10	10609ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 20:41:02	3775ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 16:16:25	8748ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 09:32:01 shown	4372ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 22:58:52	3010ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 18:56:00	8707ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 11:22:25	4125ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 07:04:38	10051ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 03:19:14	25157ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 01:13:48	877ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:45:38	2863ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:09:09	10078ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:53:20	962ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 02:43:59	931ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 02:31:42	890ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 22:30:08	8964ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 18:36:34	814ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 07:37:49	24872ms	2 NS 0 A 0 MX	❓ Unknown