janpol-construction.dk

📜 Historical scan 2026-08-19 09:55:55 · ← Latest scan

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

janpol-construction.dk is a registered .dk domain whose nameservers (dns108.ovh.net, ns108.ovh.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 11 June 2014 (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 683ms

Nameserver	IP addresses	PTR	ASN / ISP
dns108.ovh.net	2001:41d0:d01:200::2 5.196.41.157	dns108.ovh.net dns108.ovh.net	AS16276 OVH SAS AS16276 OVH SAS
ns108.ovh.net	2001:41d0:b00:fc00::2 5.135.66.229	ns108.ovh.net ns108.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#

900ms

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 02:08:46

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2014-06-11
Expires	2027-06-30 (253d)

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

683ms

649ms

708ms

AAAA

705ms

TXT

3121ms

CAA

721ms

HTTPS

721ms

TLSA

511ms

SOA

256ms

MTA-STS

833ms

DNSSEC

900ms

SRV

746ms

Total

7824ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-02 15:22:13	3421ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-01 00:55:17	3427ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 09:00:03	4427ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 16:58:29	5340ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:31:43	7054ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 10:27:28	9983ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 10:00:54	15023ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 09:55:55 shown	7824ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 09:53:59	11721ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 10:02:51	11842ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 15:33:58	10592ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 13:22:19	5219ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 05:08:00	11619ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 21:23:30	5412ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 05:23:40	5791ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 17:12:19	6750ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 00:01:02	11667ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:16:16	10555ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 12:42:44	3805ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:36:17	10367ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:49:51	11493ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:11:57	12492ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 05:26:54	3380ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 23:07:30	12386ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 11:35:14	8624ms	2 NS 0 A 0 MX	❓ Unknown