agust.dk

📜 Historical scan 2026-08-16 19:33:51 · ← Latest scan

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

agust.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 December 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#

2 records 2028ms

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#

222ms

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-16 04:05:27

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2017-12-08
Expires	2026-12-31 (65d)

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

2028ms

175ms

185ms

AAAA

139ms

TXT

603ms

CAA

185ms

HTTPS

135ms

TLSA

116ms

SOA

42ms

MTA-STS

154ms

DNSSEC

222ms

SRV

199ms

Total

2871ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-26 19:09:16	39191ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 10:38:56	1297ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 09:02:33	861ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 08:34:42	1490ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 08:21:32	5932ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 07:41:06	2922ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:15:56	2386ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 05:11:58	2943ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 19:33:51 shown	2871ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 17:36:09	55347ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 01:28:19	26539ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 19:28:48	3612ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 18:46:33	897ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 17:14:39	28820ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 20:15:09	10117ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 11:43:08	8763ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 02:17:23	8709ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 21:45:45	10067ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 09:20:09	8954ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 09:11:21	2986ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 08:54:14	2892ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 07:36:07	1071ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 03:24:43	806ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 14:19:12	8854ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 13:47:28	24858ms	2 NS 0 A 0 MX	❓ Unknown