tyrantsandkings.dk

Historical scan 2026-06-21 15:34:01  ·  ← Latest scan
Zone File Timeline & History Scan Now

tyrantsandkings.dk is a .dk domain with no delegation in this scan. It was registered on 7 January 2011 (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 10:44:01
www CNAMEtyrantsandkings.dk (all on tyrantsandkings.dk)
www vs bare domainSame network
tyrantsandkings.dk: 46.183.138.100 (AS47292)
www.tyrantsandkings.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#

275ms
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-10-30 12:13:17
FieldValue
RegistrarGIGAHOST ApS
Registered2011-01-07
Expires2028-01-31 (438d)

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
183ms
A
204ms
MX
198ms
AAAA
171ms
TXT
262ms
CAA
195ms
HTTPS
203ms
TLSA
18ms
SOA
191ms
MTA-STS
223ms
DNSSEC
275ms
SRV
199ms
Total
957ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-19 10:44:00 1030ms 5 NS 1 A 3 MX Insecure
2026-11-12 19:39:21 1663ms 5 NS 1 A 3 MX Insecure
2026-11-05 18:53:48 707ms 5 NS 1 A 3 MX Insecure
2026-11-04 18:29:23 2023ms 5 NS 1 A 3 MX Insecure
2026-11-03 17:54:05 699ms 5 NS 1 A 3 MX Insecure
2026-10-30 11:56:25 1504ms 5 NS 1 A 3 MX Insecure
2026-10-26 23:43:54 1860ms 5 NS 1 A 3 MX Insecure
2026-10-22 18:52:55 1398ms 5 NS 1 A 3 MX Insecure
2026-10-16 03:50:32 2107ms 5 NS 1 A 3 MX Insecure
2026-10-08 12:59:41 1141ms 5 NS 1 A 3 MX Insecure
2026-10-01 09:33:17 1170ms 5 NS 1 A 3 MX Insecure
2026-09-25 07:59:51 9504ms 5 NS 1 A 3 MX Insecure
2026-09-24 02:23:37 909ms 5 NS 1 A 3 MX Insecure
2026-09-21 00:59:35 1210ms 5 NS 1 A 3 MX Insecure
2026-09-10 18:22:12 1826ms 5 NS 1 A 3 MX Insecure
2026-09-07 15:40:53 750ms 5 NS 1 A 3 MX Insecure
2026-08-27 06:05:15 666ms 5 NS 1 A 3 MX Insecure
2026-08-20 18:57:05 2039ms 5 NS 1 A 3 MX Insecure
2026-08-14 10:57:27 907ms 5 NS 1 A 3 MX Insecure
2026-08-07 05:49:28 1128ms 5 NS 1 A 3 MX Insecure
2026-08-03 05:44:08 972ms 5 NS 1 A 3 MX Insecure
2026-07-24 00:25:34 16675ms 5 NS 1 A 3 MX Insecure
2026-07-16 02:09:23 1047ms 5 NS 1 A 3 MX Insecure
2026-07-02 23:27:49 1814ms 5 NS 1 A 3 MX Insecure
2026-06-25 11:30:57 2349ms 5 NS 1 A 3 MX Insecure