rebootholding.dk

Historical scan 2026-07-31 22:11:04  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

rebootholding.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 February 2016 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. We saw it become registrar-handled on 3 November 2026, when it moved from direct registration at Punktum to INWX GmbH. 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#

4 records   126ms

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 04:52:57
www185.181.104.242 (AS48596) (address records, no CNAME)
www vs bare domainSame network
rebootholding.dk: 185.181.104.242 (AS48596)
www.rebootholding.dk: 185.181.104.242 (AS48596)
WildcardYes: any name under the zone resolves

TLSA / DANE#

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

DNSSEC#

158ms
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-11-03 04:53:13
FieldValue
RegistrarINWX GmbH
Registered2016-02-02
Expires2027-02-28 (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
126ms
A
116ms
MX
115ms
AAAA
145ms
TXT
571ms
CAA
129ms
HTTPS
140ms
TLSA
120ms
SOA
113ms
MTA-STS
127ms
DNSSEC
158ms
SRV
159ms
Total
1784ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-03 04:52:57 577ms 3 NS 1 A 0 MX Insecure
2026-10-27 15:09:36 1115ms 4 NS 0 A 0 MX Unknown
2026-09-21 08:09:39 3113ms 4 NS 0 A 0 MX Unknown
2026-08-23 06:31:37 8104ms 4 NS 0 A 0 MX Unknown
2026-08-22 06:21:07 10376ms 4 NS 0 A 0 MX Unknown
2026-08-21 05:49:22 3209ms 4 NS 0 A 0 MX Unknown
2026-08-20 02:11:50 7229ms 4 NS 0 A 0 MX Unknown
2026-08-19 02:03:55 6336ms 4 NS 0 A 0 MX Unknown
2026-08-18 01:02:56 2096ms 4 NS 0 A 0 MX Unknown
2026-08-16 21:34:04 4108ms 4 NS 0 A 0 MX Unknown
2026-08-15 04:51:21 5860ms 4 NS 0 A 0 MX Unknown
2026-08-14 00:28:20 1492ms 4 NS 0 A 0 MX Unknown
2026-08-12 21:07:45 5227ms 4 NS 0 A 0 MX Unknown
2026-08-10 22:09:23 2418ms 4 NS 0 A 0 MX Unknown
2026-08-09 21:19:44 1721ms 4 NS 0 A 0 MX Unknown
2026-08-08 14:29:26 10354ms 4 NS 0 A 0 MX Unknown
2026-08-06 00:39:27 1608ms 4 NS 0 A 0 MX Unknown
2026-08-02 04:54:33 1321ms 4 NS 0 A 0 MX Unknown
2026-07-31 22:11:04 shown 1784ms 4 NS 0 A 0 MX Unknown
2026-07-28 03:15:41 10154ms 4 NS 0 A 0 MX Unknown
2026-07-27 02:59:22 9784ms 4 NS 0 A 0 MX Unknown
2026-07-26 01:57:26 9016ms 4 NS 0 A 0 MX Unknown
2026-07-25 01:27:13 9119ms 4 NS 0 A 0 MX Unknown
2026-07-23 18:43:57 1826ms 4 NS 0 A 0 MX Unknown
2026-07-22 09:22:10 1954ms 4 NS 0 A 0 MX Unknown