myibuk.dk

📜 Historical scan 2026-08-12 11:59:08 · ← Latest scan

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

myibuk.dk is a registered .dk domain whose nameservers (dns103.ovh.net, ns103.ovh.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 7 February 2013 (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 463ms

Nameserver	IP addresses	PTR	ASN / ISP
dns103.ovh.net	2001:41d0:d00:fd00::2 5.196.39.89	dns103.ovh.net dns103.ovh.net	AS16276 OVH SAS AS16276 OVH SAS
ns103.ovh.net	2001:41d0:b00:f700::2 5.135.54.65	ns103.ovh.net ns103.ovh.net	AS16276 OVH SAS AS16276 OVH SAS

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

9451ms

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-19 14:20:56

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-02-07
Expires	2027-02-28 (131d)

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

463ms

462ms

412ms

AAAA

402ms

TXT

1999ms

CAA

452ms

HTTPS

419ms

TLSA

386ms

SOA

42ms

MTA-STS

427ms

DNSSEC

9451ms

SRV

448ms

Total

11658ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 03:59:17	3532ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-25 15:02:40	4334ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-14 00:41:18	3509ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 04:10:20	6270ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 03:17:43	4300ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 03:05:18	3856ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 02:51:21	7814ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:18:13	11963ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:54:39	10298ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 08:55:07	6989ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 22:19:12	3968ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 13:51:23	11633ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 11:59:08 shown	11658ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 09:51:56	11616ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 01:21:33	6949ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 19:44:10	6030ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 20:46:35	3690ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 19:53:16	6558ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 19:14:22	3803ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:56:49	2104ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 17:57:33	11542ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 16:24:00	3798ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 14:03:20	9962ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 09:23:29	6918ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 09:16:04	2902ms	2 NS 0 A 0 MX	❓ Unknown