tidsammen.dk

Historical scan 2026-08-15 09:19:54  ·  ← Latest scan
Deactivated by the registry Zone File Timeline & History Scan Now

tidsammen.dk is a .dk domain the registry has taken out of service: it is delegated to the registry's own sentinel nameservers (nonexistent.punktum.dk), so it does not resolve. It was registered on 14 September 2026 (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#

1 records   47ms
NameserverIP addressesPTRASN / ISP
nonexistent.punktum.dk — — —

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-10-24 12:05:31
www CNAME26be240625c34d69.vercel-dns-017.com (all on vercel-dns-017.com)
www vs bare domainDifferent networks
tidsammen.dk: 46.30.211.38 (AS51468)
www.tidsammen.dk: 216.150.1.1 216.150.16.1 (AS16509)
(all like this)
WildcardNo
Denial of existenceNSEC3 · 0 iterations · no salt RFC 9276 ✓
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

TLSA / DANE#

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

DNSSEC#

99ms
CheckResult
Validation Status Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-10-24 12:17:23
FieldValue
RegistrarONE.COM A/S
Registered2026-09-14
Expires2027-09-13 (300d)

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
47ms
A
43ms
MX
59ms
AAAA
53ms
TXT
147ms
CAA
53ms
HTTPS
64ms
TLSA
24ms
SOA
52ms
MTA-STS
71ms
DNSSEC
99ms
SRV
75ms
Total
756ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-24 12:05:30 1191ms 2 NS 1 A 1 MX Secure
2026-10-07 17:46:37 283ms 2 NS 1 A 1 MX Secure
2026-09-30 09:49:16 369ms 2 NS 1 A 1 MX Secure
2026-09-23 22:24:05 2378ms 2 NS 1 A 1 MX Secure
2026-09-15 10:34:16 743ms 2 NS 1 A 1 MX Insecure
2026-08-31 05:08:34 172ms 1 NS 0 A 0 MX Unknown
2026-08-29 19:54:22 387ms 1 NS 0 A 0 MX Unknown
2026-08-28 18:42:46 483ms 1 NS 0 A 0 MX Unknown
2026-08-27 17:14:54 193ms 1 NS 0 A 0 MX Unknown
2026-08-26 17:02:39 168ms 1 NS 0 A 0 MX Unknown
2026-08-25 15:11:44 774ms 1 NS 0 A 0 MX Unknown
2026-08-24 14:36:13 176ms 1 NS 0 A 0 MX Unknown
2026-08-23 08:39:08 766ms 1 NS 0 A 0 MX Unknown
2026-08-22 08:28:57 723ms 1 NS 0 A 0 MX Unknown
2026-08-21 07:59:22 4979ms 1 NS 0 A 0 MX Unknown
2026-08-20 07:17:34 959ms 1 NS 0 A 0 MX Unknown
2026-08-19 06:24:10 929ms 1 NS 0 A 0 MX Unknown
2026-08-18 05:22:12 2595ms 1 NS 0 A 0 MX Unknown
2026-08-16 14:43:30 695ms 1 NS 0 A 0 MX Unknown
2026-08-15 09:19:54 shown 756ms 1 NS 0 A 0 MX Unknown
2026-08-14 01:41:21 8769ms 1 NS 0 A 0 MX Unknown
2026-08-12 20:31:06 3202ms 1 NS 0 A 0 MX Unknown
2026-08-11 07:06:21 1166ms 1 NS 0 A 0 MX Unknown
2026-08-09 22:04:42 1946ms 1 NS 0 A 0 MX Unknown
2026-08-08 14:59:08 2562ms 1 NS 0 A 0 MX Unknown