tidenstomrer.dk

Historical scan 2026-06-21 04:32:37  ·  ← Latest scan
Zone File Timeline & History Scan Now

tidenstomrer.dk is a .dk domain with no delegation in this scan. It was registered on 8 February 2022 (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#

No NS records found

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-19 13:58:22
www CNAMEtidenstomrer.dk (all on tidenstomrer.dk)
www vs bare domainSame network
tidenstomrer.dk: 46.183.138.100 (AS47292)
www.tidenstomrer.dk: 46.183.138.100 (AS47292)
WildcardYes: any name under the zone resolves

TLSA / DANE#

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

DNSSEC#

467ms
CheckResult
Validation StatusNot applicable: the domain has no delegation, so there is no zone to validate (stored verdict: Unknown).
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-11-12 19:05:34
FieldValue
RegistrarGIGAHOST ApS
Registered2022-02-08
Expires2027-02-07 (79d)

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
240ms
A
172ms
MX
225ms
AAAA
156ms
TXT
499ms
CAA
277ms
HTTPS
198ms
TLSA
19ms
SOA
196ms
MTA-STS
315ms
DNSSEC
467ms
SRV
319ms
Total
1159ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-19 13:58:21 2021ms 5 NS 1 A 3 MX Insecure
2026-11-12 18:59:37 589ms 5 NS 1 A 3 MX Insecure
2026-11-05 19:43:19 745ms 5 NS 1 A 3 MX Insecure
2026-10-29 11:24:15 573ms 5 NS 1 A 3 MX Insecure
2026-10-27 03:21:37 1758ms 5 NS 1 A 3 MX Insecure
2026-10-24 21:44:53 814ms 5 NS 1 A 3 MX Insecure
2026-10-23 09:31:23 1264ms 5 NS 1 A 3 MX Insecure
2026-10-16 05:08:04 2605ms 5 NS 1 A 3 MX Insecure
2026-10-08 11:28:10 2590ms 5 NS 1 A 3 MX Insecure
2026-10-02 01:00:28 3192ms 5 NS 1 A 3 MX Insecure
2026-09-24 23:52:38 854ms 5 NS 1 A 3 MX Insecure
2026-09-18 10:43:19 877ms 5 NS 1 A 3 MX Insecure
2026-09-11 08:52:08 875ms 5 NS 1 A 3 MX Insecure
2026-09-04 11:07:20 841ms 5 NS 1 A 3 MX Insecure
2026-08-28 00:37:30 1088ms 5 NS 1 A 3 MX Insecure
2026-08-27 20:30:19 723ms 5 NS 1 A 3 MX Insecure
2026-08-20 07:04:15 1166ms 5 NS 1 A 3 MX Insecure
2026-08-13 11:01:31 8986ms 5 NS 1 A 3 MX Insecure
2026-08-06 14:22:10 1042ms 5 NS 1 A 3 MX Insecure
2026-07-31 15:26:55 1779ms 5 NS 1 A 3 MX Insecure
2026-07-23 21:26:23 9918ms 5 NS 1 A 3 MX Insecure
2026-07-16 21:45:36 1499ms 5 NS 1 A 3 MX Insecure
2026-07-09 21:34:20 1562ms 5 NS 1 A 3 MX Insecure
2026-07-03 12:30:42 969ms 5 NS 1 A 3 MX Insecure
2026-06-25 11:48:24 784ms 5 NS 1 A 3 MX Insecure