aertebjerg-gaard.dk

📜 Historical scan 2026-08-20 19:36:40 · ← Latest scan

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

aertebjerg-gaard.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 9 February 2022 (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 4046ms

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#

10066ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-16 07:31:06

Field	Value
Registrar	Simply.com A/S
Registered	2022-02-09
Expires	2027-02-08 (105d)

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

4046ms

4042ms

4037ms

AAAA

4038ms

TXT

20140ms

CAA

4044ms

HTTPS

4056ms

TLSA

23ms

SOA

4056ms

MTA-STS

4061ms

DNSSEC

10066ms

SRV

4059ms

Total

31120ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-24 15:27:21	31066ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 21:21:17	1433ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:13:08	1683ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 19:48:44	1423ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 19:36:40 shown	31120ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 18:15:56	2941ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 18:11:54	8811ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 00:17:08	2215ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-15 15:14:17	3170ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-13 23:58:45	17737ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 10:21:08	905ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 21:31:53	2657ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-09 15:22:47	2570ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-02 14:10:37	53316ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 19:49:49	35128ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:48:26	891ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-27 02:25:48	16724ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 02:06:12	819ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 01:53:35	857ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 01:18:52	985ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-22 23:08:26	754ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-21 22:00:54	774ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-20 03:28:15	10117ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-18 22:16:06	8754ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-17 21:54:02	10128ms	2 NS 0 A 0 MX	⚠️ Bogus