Domain Intelligence Report
minitokyo.net
Lineage
May 26, 2007 → Oct 30, 2026Registry record since 2012 · 13 renewals on record · DNS at blicky.net · 1 nameserver change seen.
Registrar
96 snapshots
Key-Systems GmbHMijnInternetOplossing B.V.Renewed +1 yearbetween Feb 29, 2012 and Nov 12, 2013Expiry moved from 2013-01-07 to 2014-01-07, at Key-Systems GmbH.Renewed +1 yearbetween Dec 23, 2013 and Jan 7, 2014Expiry moved from 2014-01-07 to 2015-01-07, at Key-Systems GmbH.Renewed +2 yearsbetween Feb 1, 2014 and Sep 8, 2016Expiry moved from 2015-01-07 to 2017-01-07, at Key-Systems GmbH.Renewed +1 yearbetween Dec 9, 2016 and Feb 9, 2017Expiry moved from 2017-01-07 to 2018-01-07, at Key-Systems GmbH.Renewed +1 yearbetween Nov 16, 2017 and Jul 9, 2018Expiry moved from 2018-01-07 to 2019-01-07, at Key-Systems GmbH.Renewed +1 yearbetween Nov 16, 2018 and Jan 12, 2019Expiry moved from 2019-01-07 to 2020-01-07, at Key-Systems GmbH.Renewed +1 yearbetween Dec 16, 2019 and Feb 24, 2020Expiry moved from 2020-01-07 to 2021-01-07, at Key-Systems GmbH.Renewed +1 yearbetween Sep 25, 2020 and Jan 9, 2021Expiry moved from 2021-01-07 to 2022-01-07, at Key-Systems GmbH.Renewed +1 yearbetween Jan 4, 2022 and Jan 11, 2022Expiry moved from 2022-01-07 to 2023-01-07, at Key-Systems GmbH.Renewed +1 yearbetween Sep 6, 2022 and Feb 24, 2023Expiry moved from 2023-01-07 to 2024-01-07, at Key-Systems GmbH.Moved to MijnInternetOplossing B.Vbetween Jun 9, 2023 and Aug 30, 2023From Key-Systems GmbH to MijnInternetOplossing B.V, with 1 year added. Expiry moved from 2024-01-07 to 2025-01-07.Renewed +1 yearbetween Jan 8, 2025 and Feb 6, 2025Expiry moved from 2025-01-07 to 2026-01-07, at MijnInternetOplossing B.V.Renewed +1 yearbetween Jan 8, 2026 and Jan 23, 2026Expiry moved from 2026-01-07 to 2027-01-07, at MijnInternetOplossing B.V.
Nameservers
registry zone files
DNS moved to blicky.netbetween Apr 1, 2016 and Sep 3, 2016ns1.dnstools.nl, ns2.dnstools.nl → ns1.blicky.net, ns2.blicky.net.
seen in WHOIS
2011201520192026
What changed (latest 8 of 14)
- Renewed +1 year between Jan 8, 2026 and Jan 23, 2026Expiry moved from 2026-01-07 to 2027-01-07, at MijnInternetOplossing B.V.
- Renewed +1 year between Jan 8, 2025 and Feb 6, 2025Expiry moved from 2025-01-07 to 2026-01-07, at MijnInternetOplossing B.V.
- Moved to MijnInternetOplossing B.V between Jun 9, 2023 and Aug 30, 2023From Key-Systems GmbH to MijnInternetOplossing B.V, with 1 year added. Expiry moved from 2024-01-07 to 2025-01-07.
- Renewed +1 year between Sep 6, 2022 and Feb 24, 2023Expiry moved from 2023-01-07 to 2024-01-07, at Key-Systems GmbH.
- Renewed +1 year between Jan 4, 2022 and Jan 11, 2022Expiry moved from 2022-01-07 to 2023-01-07, at Key-Systems GmbH.
- Renewed +1 year between Sep 25, 2020 and Jan 9, 2021Expiry moved from 2021-01-07 to 2022-01-07, at Key-Systems GmbH.
- Renewed +1 year between Dec 16, 2019 and Feb 24, 2020Expiry moved from 2020-01-07 to 2021-01-07, at Key-Systems GmbH.
- Renewed +1 year between Nov 16, 2018 and Jan 12, 2019Expiry moved from 2019-01-07 to 2020-01-07, at Key-Systems GmbH.
Registrar and renewals: 96 WHOIS/RDAP snapshots, 2012-02-29 to 2026-04-30 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 102 .net zone-file snapshots held, 2013-10-18 to 2026-10-29.
Nameservers, WHOIS snapshots: 186 WHOIS/RDAP snapshots that listed nameservers, 2007-05-26 to 2026-06-21 (who.is archive). A change is placed between the nearest observations on either side, from whichever source made them; where the two sources disagree, both are shown.
Hatched = the span we hold records for. A coloured bar runs only between observations that named the same registrar or operator; nothing is assumed in between.
Each mark sits at the first observation of the new state; its bracket runs back to the last observation of the old one.
Gathering intelligence... (12/12)
DNS
WHOIS
Security
Email
DNSSEC
Threats
Deliverability
SSL/TLS
HTTP
Tech Stack
Subdomains
Archive
Safe
DNSSEC unsignedno attacks or spoofing
Up
HTTP 503reachable and responding
Right
Set up Page Watchit is what it is
Ready
68d aheadyou see what's coming
Outline
WHOIS
NextName B.V. d/b/a RegistrarHub · registered 22 years ago · expires Jan 7, 2027
DNS
1 A · 2 MX · 2 NS · 2 CAA · 1 SOA · 1 TXT
SSL/TLS
invalid — example.com · TLSv1.3 · expires in 3127d
Email Auth
SPF ✓ · DKIM ✗ · DMARC ✓ (p=reject)
DNSSEC
not signed
Tech Stack
Host: FranTech Solutions · Email: Self-hosted · nginx
HTTP
HTTP 503 · HSTS ✗ · CSP ✗ · X-Frame ✗ · Nosniff ✗
Security
B (180/215) · 1 high
Threats
risk: none
Deliverability
B (73/90) · 2 MX · 4 IPs · 6 issue(s)
Subdomains
wildcard DNS — every guessed name resolves
Web Archive
DNS Recordschecked 1.7d ago
Details1 A · 2 MX · 2 NS · 2 CAA · 1 SOA · 1 TXT
WHOISchecked 1.7d ago
DetailsThen vs Nownew
No card for this name. We compare then and now for domains that are in the top million and had an AboutUs page. That says nothing about this domain’s age or safety.
Check what it is now →SSL/TLSchecked 1.7d ago
DetailsInvalid certificate (self-signed)
Issuer: example.com
Protocol: TLSv1.3
Expires in 3127 days
Securitychecked 1.7d ago
DetailsB
180/215
1 high
Weakest: Basic Security, Advanced Security
Email Authchecked 1.7d ago
DetailsSPFDKIM?DMARC
Policy: reject
DNSSECchecked 1.7d ago
DetailsNot DNSSEC-signed
Tech Stackchecked 1.7d ago
DetailsFranTech SolutionsnginxEmail: Self-hosted
HTTP / Headerschecked 1.7d ago
DetailsHSTSCSPX-FrameNosniff
Threatschecked 1.7d ago
DetailsRisk: none · score 0
Zone census
Subdomainschecked 1.7d ago
Detailswildcard DNS — every name resolves, so a guessed-name inventory isn't meaningful
Click a subdomain for its full report
Web Archivechecked 1.7d ago
DetailsFirst archived: unknown
Deliverabilitychecked 1.7d ago
DetailsB
73/90 · 6 issue(s)
2 MX · 4 IP(s)
Top fix: MX IP 2001:bc8:1640:1262:dc00:ff:fe1e:406f has no PTR (reverse DNS)
Want to know when minitokyo.net changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.
Explore related
Registered in 2004 — the same year as instagram.com, vimeo.com and roblox.com.