attac.dk

📜 Historical scan 2026-08-10 00:03:46 · ← Latest scan

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

attac.dk is a registered .dk domain whose nameservers (ns1.dns-123.net, ns2.dns-123.net, ns3.dns-123.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 17 August 2017 (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 936ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.dns-123.net	35.198.132.83	83.132.198.35.bc.googleusercontent.com	AS396982 Google LLC
ns2.dns-123.net	35.187.184.173	173.184.187.35.bc.googleusercontent.com	AS396982 Google LLC
ns3.dns-123.net	35.228.54.1	1.54.228.35.bc.googleusercontent.com	AS396982 Google LLC

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

1081ms

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 01:28:06

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2017-08-17
Expires	2027-08-31 (314d)

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

936ms

913ms

984ms

AAAA

907ms

TXT

3850ms

CAA

983ms

HTTPS

897ms

TLSA

719ms

SOA

242ms

MTA-STS

984ms

DNSSEC

1081ms

SRV

949ms

Total

8544ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 01:13:40	5419ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-25 15:41:50	5752ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-25 21:23:01	5998ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 08:29:27	5518ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 05:15:45	1774ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 05:08:03	10343ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 05:03:34	9171ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:49:22	8301ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:19:40	8639ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 15:21:20	9245ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 06:17:18	7007ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 01:48:11	5605ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 06:31:09	5693ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 02:16:57	7665ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 00:03:46 shown	8544ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-04 18:27:40	5026ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 14:07:19	5675ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 10:25:46	5441ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 10:14:53	5371ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 09:50:07	5756ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 09:26:16	11484ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 05:45:50	8448ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 04:23:00	4255ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 18:20:31	21932ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 17:24:03	17577ms	3 NS 0 A 0 MX	❓ Unknown