yintang.dk

📜 Historical scan 2026-08-20 19:53:38 · ← Latest scan

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

yintang.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 3 April 2016 (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 118ms

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#

329ms

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-21 20:22:56

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2016-04-03
Expires	2027-04-30 (190d)

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

118ms

99ms

119ms

AAAA

140ms

TXT

404ms

CAA

117ms

HTTPS

133ms

TLSA

96ms

SOA

74ms

MTA-STS

153ms

DNSSEC

329ms

SRV

175ms

Total

1507ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-28 08:37:16	10166ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-18 11:36:07	49260ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 14:28:19	3080ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 20:59:51	3234ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 20:20:24	10084ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 20:05:48	3135ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 19:53:38 shown	1507ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 18:36:30	4616ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 18:32:28	26411ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 17:29:36	27207ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 17:10:46	1538ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 12:07:39	864ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 02:36:32	27235ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 21:03:22	10203ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 21:12:40	3466ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 15:09:11	905ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 07:02:08	10092ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 16:00:51	967ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 15:16:27	1416ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:59:47	8799ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:53:35	10033ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:58:27	1008ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 18:28:39	8768ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 13:41:16	929ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 12:44:14	8878ms	2 NS 0 A 0 MX	❓ Unknown