aftc-ml.dk

📜 Historical scan 2026-07-03 01:25:38 · ← Latest scan

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

aftc-ml.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 1 December 2015 (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 99ms

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#

135ms

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-09 09:25:26

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

📋 WHOIS#

⏱️ Lookup Timing#

99ms

86ms

AAAA

98ms

TXT

407ms

CAA

130ms

HTTPS

96ms

TLSA

81ms

SOA

109ms

MTA-STS

90ms

DNSSEC

135ms

SRV

111ms

Total

828ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-26 22:33:23	9989ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 04:46:09	6177ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 04:40:18	4839ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:23:58	4331ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 03:58:29	5940ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:24:15	6811ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 23:33:07	4291ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 16:39:32	2435ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 09:39:33	1552ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 07:30:54	16891ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 02:02:16	16777ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 21:32:52	10213ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 16:31:19	1548ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 08:04:36	1466ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 09:21:01	10426ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:33:46	776ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 06:22:57	10029ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 06:17:54	756ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 05:44:15	10072ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 05:18:02	1528ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 22:59:35	783ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 21:58:18	800ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 21:33:49	10324ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 21:13:07	837ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 18:27:03	8863ms	2 NS 0 A 0 MX	❓ Unknown