wachmannconsulting.dk

📜 Historical scan 2026-07-04 09:26:10 · ← Latest scan

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

wachmannconsulting.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 July 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#

4 records 49ms

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#

132ms

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-26 03:01:14

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2015-07-06
Expires	2027-07-31 (278d)

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

49ms

62ms

63ms

AAAA

62ms

TXT

189ms

CAA

60ms

HTTPS

69ms

TLSA

42ms

SOA

139ms

MTA-STS

73ms

DNSSEC

132ms

SRV

66ms

Total

783ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-24 01:32:03	1015ms	4 NS 0 A 0 MX	❓ Unknown
2026-10-09 09:08:41	2839ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-29 18:48:08	868ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-23 12:55:10	2815ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-23 18:29:10	3401ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 13:48:16	9568ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 13:41:16	4104ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-20 13:36:07	10275ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:57:59	1271ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-18 00:35:08	9230ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-16 13:31:09	8998ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-15 09:25:17	2880ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-13 14:10:46	10358ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-12 12:38:03	10391ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-11 02:00:01	10440ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-08 12:06:47	2845ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-29 06:22:47	9936ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 08:05:43	1243ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 06:46:50	1144ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 06:27:03	15440ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 06:15:36	9954ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-23 05:15:48	1268ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 04:55:22	1208ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-20 23:25:52	1071ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-19 06:13:50	1315ms	4 NS 0 A 0 MX	❓ Unknown