a-consults.dk

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

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

a-consults.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 4 August 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#

2 records 77ms

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#

221ms

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-18 17:55:56

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-08-04
Expires	2027-08-31 (311d)

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

77ms

74ms

80ms

AAAA

60ms

TXT

240ms

CAA

98ms

HTTPS

99ms

TLSA

70ms

SOA

40ms

MTA-STS

126ms

DNSSEC

221ms

SRV

135ms

Total

1155ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 01:53:41	1242ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-09 15:14:07	9954ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 16:18:42	10211ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 18:00:44	3661ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 16:27:10	9312ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 08:35:34	1356ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 08:27:52	4489ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 06:20:08	11041ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:51:23	3095ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 00:17:21	2710ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 06:14:03	1790ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 13:49:36	1482ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 00:40:47	10144ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 21:26:39	2986ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 20:36:33	1398ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 05:02:44	1424ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 10:26:30	1014ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 19:22:43	986ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 19:15:57	802ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 18:53:38	838ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 18:35:12	941ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:03:27	1385ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:41:34	10031ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:11:18	828ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 12:30:09	1002ms	2 NS 0 A 0 MX	❓ Unknown