acrasch.dk

📜 Historical scan 2026-07-23 19:16:07 · ← Latest scan

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

acrasch.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 8 May 2003 (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 36ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com A/S

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

117ms

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 08:31:26

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2003-05-08
Expires	2027-05-31 (218d)

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

36ms

44ms

39ms

AAAA

46ms

TXT

299ms

CAA

44ms

HTTPS

52ms

TLSA

50ms

SOA

37ms

MTA-STS

70ms

DNSSEC

117ms

SRV

160ms

Total

852ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-28 05:33:35	10091ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 07:39:17	1542ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:51:15	1893ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:27:56	4627ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:22:43	987ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 05:40:54	9788ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:52:17	4190ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 22:26:21	31162ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 22:16:48	3026ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 21:56:31	867ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 22:25:57	977ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 17:51:01	2709ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 06:14:02	4082ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 04:32:38	3058ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 06:00:28	2469ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 05:14:42	2445ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 00:49:18	1497ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:36:00	745ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:48:42	1388ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:31:33	832ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 21:53:41	1338ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 19:16:07 shown	852ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:25:20	853ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 11:23:04	1701ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 08:03:34	910ms	2 NS 0 A 0 MX	❓ Unknown