skalo.dk

📜 Historical scan 2026-07-04 14:38:55 · ← Latest scan

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

skalo.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 12 October 2023 (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 418ms

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 2001:67c:750::4	ns3.inleed.net ns3.inleed.net	AS206170 Yelles AB 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#

2439ms

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-23 06:17:01

Field	Value
Registrar	Key-Systems GmbH
Registered	2023-10-12
Expires	2027-10-11 (352d)

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

418ms

398ms

430ms

AAAA

352ms

TXT

1535ms

CAA

352ms

HTTPS

424ms

TLSA

282ms

SOA

422ms

MTA-STS

516ms

DNSSEC

2439ms

SRV

493ms

Total

7384ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 23:31:22	13514ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 22:42:38	8267ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 22:40:08	3783ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 22:29:48	4559ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 21:50:39	8499ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:16:32	12611ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 14:55:33	6782ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 02:22:33	7512ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 22:13:03	3367ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 17:14:05	27391ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 14:47:39	8526ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 01:44:38	9975ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 15:01:31	25482ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 06:30:30	3906ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:19:35	17047ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:49:58	4344ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 21:59:36	11822ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 21:37:05	5805ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 18:21:45	12994ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 12:05:42	4368ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 04:23:38	17175ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 02:40:41	9176ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 15:22:24	9154ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-17 15:07:06	17553ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-15 03:59:47	9229ms	3 NS 0 A 0 MX	❓ Unknown