lamrou.dk

📜 Historical scan 2026-07-17 16:29:01 · ← Latest scan

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

lamrou.dk is a registered .dk domain whose nameservers (dns109.ovh.net, ns109.ovh.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 13 February 2019 (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 916ms

Nameserver	IP addresses	PTR	ASN / ISP
dns109.ovh.net	2001:41d0:d01:300::2 5.196.41.217	dns109.ovh.net dns109.ovh.net	AS16276 OVH SAS AS16276 OVH SAS
ns109.ovh.net	2001:41d0:b00:fd00::2 5.135.67.9	ns109.ovh.net ns109.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#

1014ms

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-14 21:29:47

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2019-02-13
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#

916ms

193ms

AAAA

922ms

TXT

1845ms

CAA

920ms

HTTPS

187ms

TLSA

173ms

SOA

27ms

MTA-STS

148ms

DNSSEC

1014ms

SRV

2682ms

Total

4523ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-27 08:13:27	12201ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-23 07:31:46	12110ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-08 05:25:11	12088ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 03:10:26	4571ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 09:39:56	3975ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 16:10:27	8488ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 16:02:34	4580ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:31:17	8150ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 08:04:58	8023ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 07:47:39	5871ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 14:04:49	3417ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 07:00:35	8927ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 15:59:42	11776ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 15:45:49	7056ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 15:20:11	3806ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 10:14:43	3857ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 20:43:15	8371ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 05:58:14	3982ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 11:23:57	6977ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:39:09	5856ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 00:09:25	27348ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 23:49:45	14717ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 23:19:07	2815ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 23:03:56	15133ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:34:08	2273ms	2 NS 0 A 0 MX	❓ Unknown