dermatude.dk

📜 Historical scan 2026-08-24 02:01:02 · ← Latest scan

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

dermatude.dk is a registered .dk domain whose nameservers (ns-3.eu, ns1.hix.nl, ns2.hix.nl) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 15 December 2015 (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 2823ms

Nameserver	IP addresses	PTR	ASN / ISP
ns-3.eu	2a01:7c8:d007:462::155 85.10.135.155	ns-3.eu ns-3.eu	AS20857 Signet B.V. AS20857 Signet B.V.
ns1.hix.nl	2a00:a0c0:3::1:2 83.137.192.101	ns1.hix.nl ns1.hix.nl	AS34233 Superior B.V. AS34233 Superior B.V.
ns2.hix.nl	31.3.110.75	ns2.hix.nl	AS197731 The Internet Engineering Group 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#

3658ms

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

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2015-12-15
Expires	2026-12-31 (74d)

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

2823ms

3506ms

2959ms

AAAA

3464ms

TXT

6537ms

CAA

3459ms

HTTPS

2836ms

TLSA

870ms

SOA

78ms

MTA-STS

3003ms

DNSSEC

3658ms

SRV

3741ms

Total

11207ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 12:24:10	11854ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-30 15:36:58	13493ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-26 15:16:31	14480ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-05 09:53:33	15181ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 02:01:02 shown	11207ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 22:17:46	18242ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 22:07:24	5625ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 21:54:13	2936ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 21:39:49	19459ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:24:04	17846ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 13:30:19	14337ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 02:29:49	16583ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 01:16:35	17352ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 21:22:27	17931ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 02:13:27	13695ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 22:23:27	13837ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 16:05:17	2718ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 00:23:47	3221ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-30 08:33:29	22933ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:22:56	2445ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:42:53	3372ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:21:30	10101ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:08:56	3445ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 13:56:11	2538ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 13:04:51	3026ms	3 NS 0 A 0 MX	❓ Unknown