aagaard-fourage.dk

📜 Historical scan 2026-08-07 09:04:05 · ← Latest scan

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

aagaard-fourage.dk is a registered .dk domain whose nameservers (ns1.danaweb.org, ns2.danaweb.org, ns3.danaweb.org and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 6 January 2004 (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#

4 records 108ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.danaweb.org	185.25.141.12	ns1.curanet.dk	AS48854 team.blue Denmark A/S
ns2.danaweb.org	91.197.248.75	ns2.curanet.dk	AS48854 team.blue Denmark A/S
ns3.danaweb.org	185.25.141.12	ns1.curanet.dk	AS48854 team.blue Denmark A/S
ns4.danaweb.org	91.197.248.75	ns2.curanet.dk	AS48854 team.blue Denmark 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#

157ms

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-20 11:31:27

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-01-06
Expires	2027-01-31 (102d)

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

108ms

93ms

88ms

AAAA

87ms

TXT

337ms

CAA

95ms

HTTPS

100ms

TLSA

61ms

SOA

36ms

MTA-STS

94ms

DNSSEC

157ms

SRV

103ms

Total

1340ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 19:22:34	1056ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-27 20:48:53	1240ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-23 05:30:00	2010ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 05:10:31	1784ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:53:52	1575ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:05:41	9601ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:24:51	7406ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-17 06:00:44	4238ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-15 20:40:20	9332ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-14 11:49:42	1252ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-11 17:36:28	9752ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-10 16:33:31	4620ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-09 15:27:02	1310ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-07 09:04:05 shown	1340ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-29 11:29:58	9915ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:14:49	8870ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 01:50:14	1122ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 01:22:51	8964ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 01:02:24	1253ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 00:21:37	992ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:53:57	1000ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-21 19:24:23	9179ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-20 06:47:24	9977ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-19 05:09:04	1458ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-18 03:27:07	1343ms	4 NS 0 A 0 MX	❓ Unknown