soliduct.dk

📜 Historical scan 2026-07-25 12:47:38 · ← Latest scan

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

soliduct.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 7 April 2025 (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 90ms

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#

218ms

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-21 09:23:49

Field	Value
Registrar	Key-Systems GmbH
Registered	2025-04-07
Expires	2027-04-06 (167d)

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

90ms

88ms

AAAA

83ms

TXT

552ms

CAA

84ms

HTTPS

79ms

TLSA

79ms

SOA

33ms

MTA-STS

196ms

DNSSEC

218ms

SRV

296ms

Total

9337ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-27 09:06:01	11308ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 12:10:46	6050ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 11:38:00	10042ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 11:24:51	9957ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 10:27:31	3410ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 08:43:46	1465ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 08:33:33	2385ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 17:40:31	19425ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 05:34:31	3932ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:43:36	11275ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 11:14:58	5021ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 04:45:29	8096ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 22:51:32	3847ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-04 08:51:33	11443ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 05:33:24	4668ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-01 17:30:22	14964ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 03:34:18	11407ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:52:27	3305ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 13:06:10	33430ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:47:38 shown	9337ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:49:19	1405ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:47:05	1595ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 09:12:43	4262ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 02:52:44	9317ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 14:13:31	9391ms	3 NS 0 A 0 MX	❓ Unknown