act2perform.dk

📜 Historical scan 2026-08-23 05:26:50 · ← Latest scan

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

act2perform.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 5 December 2010 (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 124ms

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#

166ms

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-25 03:46:28

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2010-12-05
Expires	2026-12-31 (67d)

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

124ms

119ms

83ms

AAAA

106ms

TXT

8340ms

CAA

83ms

HTTPS

71ms

TLSA

45ms

SOA

33ms

MTA-STS

65ms

DNSSEC

166ms

SRV

130ms

Total

9067ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 14:48:50	1277ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-25 11:11:53	9963ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 09:21:09	10030ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 10:22:50	10190ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 05:26:50 shown	9067ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 05:11:18	17074ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:55:45	1537ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:39:27	2205ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:24:10	5553ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 00:00:51	10196ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 14:54:58	4191ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 09:31:06	8718ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 21:35:43	923ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 10:02:12	29439ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 04:57:31	945ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 18:56:34	2387ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:54:30	2423ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:24:27	8864ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:56:33	848ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:21:05	10214ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 14:37:28	873ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 14:28:28	1385ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 09:56:37	902ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 06:47:03	822ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 16:24:07	10045ms	2 NS 0 A 0 MX	❓ Unknown