websyn.dk

📜 Historical scan 2026-08-24 00:39:34 · ← Latest scan

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

websyn.dk is a registered .dk domain whose nameservers (ns1.wannafind.dk, ns2.wannafind.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 6 January 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 256ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.wannafind.dk	185.25.141.6 2a02:2339:4006:103:1c:3f6d:daba:dee	ns1.wannafind.dk ns1.wannafind.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.wannafind.dk	2a02:2339:1:104::daba:daa 91.197.248.69	ns2.wannafind.dk ns2.wannafind.dk	AS48854 team.blue Denmark A/S 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#

387ms

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-25 07:20:51

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

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

256ms

278ms

266ms

AAAA

247ms

TXT

1294ms

CAA

269ms

HTTPS

265ms

TLSA

214ms

SOA

69ms

MTA-STS

271ms

DNSSEC

387ms

SRV

277ms

Total

3866ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-24 13:34:12	1216ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 14:28:50	861ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-24 01:42:36	2896ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 00:39:34 shown	3866ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:17:46	1718ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:14:21	9034ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 23:52:13	1834ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:23:01	9358ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:27:25	23859ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 12:46:00	10050ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 09:13:15	4660ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 10:21:40	1175ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 12:42:34	9099ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 10:38:53	9949ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 19:43:21	10003ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 06:09:33	9979ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 10:26:25	2427ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 04:38:30	5225ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:02:07	9326ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:31:40	1132ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 23:21:41	1016ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 23:12:55	1274ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 22:36:21	9912ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 22:16:55	9869ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 10:32:08	9282ms	2 NS 0 A 0 MX	❓ Unknown