ajour4you.dk

📜 Historical scan 2026-07-14 21:21:00 · ← Latest scan

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

ajour4you.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 6 February 2014 (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 152ms

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#

180ms

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-27 18:49:27

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2014-02-06
Expires	2027-02-28 (123d)

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

152ms

173ms

137ms

AAAA

174ms

TXT

636ms

CAA

172ms

HTTPS

173ms

TLSA

120ms

SOA

16ms

MTA-STS

152ms

DNSSEC

180ms

SRV

175ms

Total

1487ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-29 15:13:02	1831ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 21:35:42	1354ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 04:40:32	1600ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:13:02	6146ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 20:10:59	6044ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 20:08:43	1669ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 19:30:02	3765ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 19:27:46	10407ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 16:25:14	3181ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 22:34:48	8854ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 09:57:21	16859ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 05:15:24	2962ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 21:40:19	8905ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 11:31:55	1398ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:28:18	10060ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 18:17:09	831ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 18:04:00	10052ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:15:29	1507ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:34:39	870ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:33:38	8642ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 14:05:37	912ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 23:29:56	10038ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 20:26:00	815ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 19:17:39	945ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-16 10:58:27	10041ms	2 NS 0 A 0 MX	❓ Unknown