leofoto.dk

📜 Historical scan 2026-07-12 14:51:14 · ← Latest scan

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

leofoto.dk is a registered .dk domain whose nameservers (ns01.is.nl, ns02.is.nl, ns03.is.nl) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 26 July 2018 (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 10204ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.is.nl	213.75.63.33 2a02:a47f:ac:1::1153	ns1.widexs.nl ns11.kpn.net	AS1136 KPN B.V. AS1136 KPN B.V.
ns02.is.nl	213.75.63.68 2a02:a47f:ac:1::1253	ns2.widexs.nl ns12.kpn.net	AS1136 KPN B.V. AS1136 KPN B.V.
ns03.is.nl	213.75.63.34 2a02:a47f:ac:1::1353	ns13.kpn.net ns13.kpn.net	AS1136 KPN B.V. AS1136 KPN 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#

16061ms

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 04:27:40

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2018-07-26
Expires	2027-07-31 (283d)

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

10204ms

8042ms

8328ms

AAAA

16043ms

TXT

1321ms

CAA

185ms

HTTPS

194ms

TLSA

237ms

SOA

28ms

MTA-STS

492ms

DNSSEC

16061ms

SRV

16045ms

Total

22569ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 18:34:40	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 18:07:15	33006ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:57:45	11979ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 17:50:58	40142ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:08:56	50887ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 04:39:31	46487ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 10:21:57	44473ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 12:50:41	48653ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 17:57:45	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 14:36:24	46727ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 19:00:33	49438ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 07:37:00	12663ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-02 08:37:55	19744ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 22:29:35	47026ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 14:10:51	33094ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 10:59:36	43172ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 10:36:51	46159ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 10:09:28	53635ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 09:39:17	46863ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 09:11:58	7664ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 12:50:49	34837ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 04:53:54	36031ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 00:39:58	46539ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-17 20:42:42	42048ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-13 16:29:25	2833ms	3 NS 0 A 0 MX	❓ Unknown