inquisitor.dk

📜 Historical scan 2026-07-26 16:57:36 · ← Latest scan

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

inquisitor.dk is a registered .dk domain whose nameservers (ns01.servage.net, ns02.servage.net, ns03.servage.net and 2 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 June 2005 (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#

5 records 31ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.servage.net	—	—	—
ns02.servage.net	—	—	—
ns03.servage.net	—	—	—
ns04.servage.net	—	—	—
ns05.servage.net	—	—	—

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

116ms

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-18 20:57:04

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2005-06-02
Expires	2027-06-30 (252d)

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

31ms

37ms

56ms

AAAA

46ms

TXT

887ms

CAA

48ms

HTTPS

60ms

TLSA

193ms

SOA

29ms

MTA-STS

59ms

DNSSEC

116ms

SRV

16055ms

Total

17389ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-27 21:32:10	1755ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-28 11:17:20	2202ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-23 23:59:10	1537ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-22 22:24:46	1765ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-21 22:16:43	7008ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-20 21:58:45	7805ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-19 21:25:42	2976ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-18 20:59:24	2698ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-17 20:49:39	1774ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-16 09:37:02	3343ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-14 19:12:29	1738ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-12 22:29:54	3831ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-09 17:18:34	9550ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-07 17:07:32	1875ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-06 10:44:36	1922ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-03 09:44:52	11359ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:27:04	10104ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-26 16:57:36 shown	17389ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-25 16:33:27	5669ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-24 15:55:02	9695ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-23 15:20:18	17568ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-22 11:33:03	1670ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-21 07:42:48	9525ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-19 20:27:52	10364ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-18 16:06:36	2903ms	5 NS 0 A 0 MX	❓ Unknown