agencium.dk

📜 Historical scan 2026-09-01 15:59:46 · ← Latest scan

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

agencium.dk is a registered .dk domain whose nameservers (dns102.ovh.net, ns102.ovh.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 9 August 2012 (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 1116ms

Nameserver	IP addresses	PTR	ASN / ISP
dns102.ovh.net	2001:41d0:d00:fc00::2 5.196.38.181	dns102.ovh.net dns102.ovh.net	AS16276 OVH SAS AS16276 OVH SAS
ns102.ovh.net	2001:41d0:b00:f600::2 5.135.54.1	ns102.ovh.net ns102.ovh.net	AS16276 OVH SAS AS16276 OVH SAS

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

1135ms

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-24 13:16:47

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2012-08-09
Expires	2027-08-31 (310d)

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

1116ms

995ms

6554ms

AAAA

897ms

TXT

3021ms

CAA

918ms

HTTPS

145ms

TLSA

375ms

SOA

1092ms

MTA-STS

1518ms

DNSSEC

1135ms

SRV

0ms

Total

20543ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-03 22:27:01	11658ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-01 15:59:46 shown	20543ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 09:47:08	4134ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 04:43:47	3809ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 04:19:55	5563ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 03:57:29	11060ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 00:49:24	3023ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:38:10	9367ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 19:25:26	8440ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 11:36:01	9532ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 08:59:45	4003ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 17:10:45	6367ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 16:24:00	5037ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 19:55:29	6143ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 14:16:25	13944ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 09:07:37	6993ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 09:54:41	8156ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:39:33	9791ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:05:00	11682ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 16:46:50	3801ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 16:26:46	15684ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 12:18:08	6326ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 11:44:32	2859ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 07:43:35	2646ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 06:40:23	6661ms	2 NS 0 A 0 MX	❓ Unknown