asman.dk

📜 Historical scan 2026-07-29 16:44:32 · ← Latest scan

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

asman.dk is a registered .dk domain whose nameservers (ns.talkactive.net, ns2.talkactive.net, vennely.jth.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 May 2003 (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#

3 records 4030ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.talkactive.net	—	—	—
ns2.talkactive.net	—	—	—
vennely.jth.net	212.237.178.27 2a06:4005:8003::2	mail.jth.net jth.net	AS204151 EWII Bredbaand A/S AS204151 EWII Bredbaand 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#

10071ms

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 22:43:20

Field	Value
Registrar	1API GmbH
Registered	2003-05-02
Expires	2027-05-31 (226d)

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

4030ms

4031ms

4021ms

AAAA

4019ms

TXT

20133ms

CAA

4030ms

HTTPS

4031ms

TLSA

23ms

SOA

15ms

MTA-STS

4042ms

DNSSEC

10071ms

SRV

4031ms

Total

28439ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 22:12:05	26000ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-29 16:14:16	24688ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-23 12:47:25	47589ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 09:02:35	1811ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 08:49:24	3577ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 08:43:31	25213ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 07:43:37	28279ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:45:57	60946ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 20:09:02	20621ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 13:08:44	21472ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 06:22:17	1894ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 16:41:21	26039ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 09:31:12	24382ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 11:12:40	28546ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-31 13:08:28	10232ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 16:44:32 shown	28439ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:39:00	8921ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:52:13	1247ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:22:51	17067ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 21:43:49	16968ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 21:21:52	17067ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:31:26	28908ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 14:49:39	28403ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 09:31:24	17193ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 01:44:48	9299ms	3 NS 0 A 0 MX	❓ Unknown