orlaco.dk

📜 Historical scan 2026-07-19 13:34:57 · ← Latest scan

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

orlaco.dk is a registered .dk domain whose nameservers (ns03.2is.nl, ns04.2is.nl) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 November 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 285ms

Nameserver	IP addresses	PTR	ASN / ISP
ns03.2is.nl	2001:1460:3:4:1c00:b4ff:fe00:270a 62.221.202.199	ns03.2is.nl ns03.2is.nl	AS48635 Your Hosting B.V. AS48635 Your Hosting B.V.
ns04.2is.nl	2001:1460:2:2:1c00:4eff:fe00:2bf6 62.221.197.54	ns04.2is.be ns04.2is.be	AS48635 Your Hosting B.V. AS48635 Your Hosting B.V.

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

9324ms

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-17 11:56:13

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2007-11-02
Expires	2026-11-30 (42d)

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

285ms

314ms

283ms

AAAA

274ms

TXT

1424ms

CAA

284ms

HTTPS

283ms

TLSA

288ms

SOA

23ms

MTA-STS

291ms

DNSSEC

9324ms

SRV

287ms

Total

11091ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 11:43:04	3328ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 23:32:17	12265ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 16:02:24	11910ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:29:14	11250ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:14:46	1774ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 05:58:08	2741ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 05:39:49	1890ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:10:43	5129ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 12:59:10	4807ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 09:00:29	5048ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 23:38:52	4071ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 12:46:22	2578ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 21:12:02	3336ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 05:41:02	11379ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 17:27:03	2999ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 16:16:19	2978ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 11:58:12	11260ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 11:39:31	4569ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 11:15:14	10454ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 10:17:36	3652ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 09:55:58	10671ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 08:10:23	4133ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 04:06:31	4665ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 13:34:57 shown	11091ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 10:40:03	4062ms	2 NS 0 A 0 MX	❓ Unknown