Alternatives to keylocker.io
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
keylocker.io was registered with NameCheap, Inc. on 24 Jan 2024. Its SSL certificate from Google Trust Services is valid until 28 Jan 2027, and the site supports HTTP/3.
On-page basics for the homepage.
Networks cache previews — changes can take time to show.
What security vendors and the WOT community say about this domain.
1 of 5 protections set up
Lists the servers allowed to send email for this domain.
v=spf1 include:spf.improvmx.com include:_spf.google.com ~allNo key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
0 of 6 recommended headers
Forces HTTPS on future visits.
Limits where scripts can load from — the main defence against XSS.
Stops the site being framed for clickjacking.
Prevents browsers guessing file types.
Which AI crawlers this site allows, and whether it publishes an llms.txt.
From robots.txt. “Partly blocked”: kept out of some pages, not the homepage. Not every crawler follows it. llms.txt is an optional guide some sites publish for AI assistants — it is not a ranking factor.
Pages and files that show who runs the site and how it handles data.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
8 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| keylocker.shop | Other extension | 17 Oct 2026 | Checking… | Report → |
| keylocker.dev | Other extension | 10 Sept 2026 | Checking… | Report → |
| keylocker.pro | Other extension | 8 Sept 2026 | Checking… | Report → |
| weylocker.shop | Typo | 21 Oct 2026 | Checking… | Report → |
| keelocker.com | Typo | 6 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is keylocker.io’s name taken on other extensions?
Every IP address keylocker.io resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| keylocker.io | 172.64.80.1 | 282 |
| Host | IPv6 address | TTL |
|---|---|---|
| keylocker.io | 2606:4700:3034::ac43:d2a1 | 300 |
| keylocker.io | 2606:4700:3035::6815:3d84 | 300 |
| Host | Mail server | TTL |
|---|---|---|
| keylocker.io | 1 aspmx.l.google.com | 3600 |
| keylocker.io | 5 alt1.aspmx.l.google.com | 3600 |
| keylocker.io | 5 alt2.aspmx.l.google.com | 3600 |
| keylocker.io | 10 alt3.aspmx.l.google.com | 3600 |
| keylocker.io | 10 alt4.aspmx.l.google.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| keylocker.io | cortney.ns.cloudflare.com | 86400 |
| keylocker.io | maxim.ns.cloudflare.com | 86400 |
| Host | Text | TTL |
|---|---|---|
| keylocker.io | "google-site-verification=OrOfMj-jBozCg8mJvpshuVXPkgLuzlfM8RdMf3jRXSg" | 3600 |
| keylocker.io | "v=spf1 include:spf.improvmx.com include:_spf.google.com ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| keylocker.io | cortney.ns.cloudflare.com dns.cloudflare.com 2418820395 10000 2400 604800 1800 | 1800 |
Other domains served from 2606:4700:3034::ac43:d2a1. Normal for shared hosting and CDNs.
No reviews yet. Used keylocker.io? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
keylocker.io has no community safety rating yet, and it isn't on any of the 6 blocklists we check. Its SSL certificate is valid until 28 Jan 2027. See Security →
keylocker.io is registered through NameCheap, Inc. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expires on 24 Jan 2027 — in 2 months. See Overview →
keylocker.io was registered on 24 Jan 2024, making it 2 years old. See Overview →
keylocker.io is served from 4 IP addresses, mainly on AS13335. See Hosting →
Raw registry data for keylocker.io. May be redacted by privacy services.
Domain Name: keylocker.io Registry Domain ID: REDACTED Registrar WHOIS Server: whois.namecheap.com Registrar URL: https://www.namecheap.com/ Updated Date: 2026-08-11T20:25:30Z Creation Date: 2024-01-24T13:44:43Z Registry Expiry Date: 2027-01-24T13:44:43Z Registrar: NameCheap, Inc. Registrar IANA ID: 1068 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.9854014545 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: REDACTED Registrant Name: REDACTED Registrant Organization: Privacy service provided by WITHHELD FOR PRIVACY LLC Registrant Street: REDACTED Registrant City: REDACTED Registrant State/Province: Delaware Registrant Postal Code: REDACTED Registrant Country: US Registrant Phone: REDACTED Registrant Phone Ext: REDACTED Registrant Fax: REDACTED Registrant Fax Ext: REDACTED Registrant Email: REDACTED Registry Admin ID: REDACTED Admin Name: REDACTED Admin Organization: REDACTED Admin Street: REDACTED Admin City: REDACTED Admin State/Province: REDACTED Admin Postal Code: REDACTED Admin Country: REDACTED Admin Phone: REDACTED Admin Phone Ext: REDACTED Admin Fax: REDACTED Admin Fax Ext: REDACTED Admin Email: REDACTED Registry Tech ID: REDACTED Tech Name: REDACTED Tech Organization: REDACTED Tech Street: REDACTED Tech City: REDACTED Tech State/Province: REDACTED Tech Postal Code: REDACTED Tech Country: REDACTED Tech Phone: REDACTED Tech Phone Ext: REDACTED Tech Fax: REDACTED Tech Fax Ext: REDACTED Tech Email: REDACTED Name Server: cortney.ns.cloudflare.com Name Server: maxim.ns.cloudflare.com DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/ >>> Last update of WHOIS database: 2026-11-04T19:56:44Z <<< For more information on Whois status codes, please visit https://icann.org/epp Terms of Use: Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or the Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. When using the Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Identity Digital Inc. and Registry Operator reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
The first response from http://www.keylocker.io, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with keylocker.io. Data is collected independently from public sources and some figures are estimates, provided for information only.
Controls how much of the URL is shared with other sites.
Restricts camera, microphone and other browser features.
From the homepage's response, https://keylocker.io/
Spam and malware blocklists for the site's IP and mail servers.
0 of 6 blocklists list this domain's IP or mail servers.
Found in public certificate transparency logs.
No subdomains found in the certificate transparency logs.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 4 Nov 2026.