tsnet.dk

Historical scan 2026-09-20 17:29:16  ·  ← Latest scan
Zone File Timeline & History Scan Now

tsnet.dk is a .dk domain served by 2 nameservers (lila.ns.cloudflare.com, mario.ns.cloudflare.com). It was registered on 27 February 2023 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is not DNSSEC-signed, has no DMARC policy and has no IPv6 address. 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   136ms

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

Web & zone#

latest probe, not this scan · checked 2026-11-03 07:48:56
wwwNXDOMAIN
www vs bare domainNeither resolves
tsnet.dk: no address
www.tsnet.dk: no address
WildcardNo

ACME Challenge#

TypeNameValue
TXT _acme-challenge.tsnet.dk PCoj0gAZdFI2IiMAVJsXS8nRTvES4SMlWOmFh5YlOTg
TXT _acme-challenge.tsnet.dk S8ZOXchU-qaI8QIYQidYoxSNj4B_UwKs4_hev3BIVdY

TLSA / DANE#

No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

DNSSEC#

174ms
CheckResult
Validation Status Insecure
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: ncache nxrrset

SOA#

0ms
FieldValue
Serial2415183550
Primary NS (MNAME)lila.ns.cloudflare.com
Responsible (RNAME)dns@cloudflare.com
Refresh10000s
Retry2400s
Expire604800s
Minimum (neg-cache TTL)1800s

Registration#

WHOIS fetched 2026-10-30 23:31:05
FieldValue
RegistrarDomeneshop AS
Registered2023-02-27
Expires2027-02-26 (101d)

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#

NS
136ms
A
94ms
MX
150ms
AAAA
131ms
TXT
343ms
CAA
137ms
HTTPS
134ms
TLSA
34ms
SOA
0ms
MTA-STS
161ms
DNSSEC
174ms
SRV
161ms
Total
771ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-03 07:48:56 376ms 2 NS 0 A 0 MX Insecure
2026-10-30 23:28:49 348ms 2 NS 0 A 0 MX Insecure
2026-10-28 02:47:23 339ms 2 NS 0 A 0 MX Insecure
2026-10-26 19:59:30 328ms 2 NS 0 A 0 MX Insecure
2026-10-03 05:54:54 779ms 2 NS 0 A 0 MX Insecure
2026-09-28 05:00:07 520ms 2 NS 0 A 0 MX Insecure
2026-09-22 01:26:02 872ms 2 NS 0 A 0 MX Insecure
2026-09-20 17:29:16 shown 771ms 2 NS 0 A 0 MX Insecure
2026-09-13 16:19:46 1012ms 2 NS 0 A 0 MX Insecure
2026-09-13 07:18:17 2300ms 2 NS 0 A 0 MX Insecure
2026-09-09 08:33:38 593ms 2 NS 0 A 0 MX Insecure
2026-08-27 02:19:29 531ms 2 NS 0 A 0 MX Insecure
2026-08-26 18:42:26 410ms 2 NS 0 A 0 MX Insecure
2026-08-22 05:02:57 8836ms 2 NS 0 A 0 MX Insecure
2026-07-04 22:45:16 1317ms 2 NS 0 A 0 MX Insecure
2026-07-03 20:13:47 10411ms 2 NS 0 A 0 MX Insecure
2026-06-28 09:40:26 987ms 2 NS 0 A 0 MX Insecure
2026-06-23 18:18:14 1721ms 2 NS 0 A 0 MX Insecure
2026-06-22 20:23:33 996ms 0 NS 0 A 0 MX Unknown
2026-06-21 23:43:10 401ms 2 NS 0 A 0 MX Insecure
2026-06-20 04:10:31 532ms 2 NS 0 A 0 MX Bogus
2026-06-17 13:10:06 2324ms 2 NS 0 A 0 MX Insecure