Alternatives to ipfs.tech
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
ipfs.tech was registered with CSC Corporate Domains Inc. on 27 May 2020 and is hosted on AS60068 DataCamp Limited in Japan. Its SSL certificate from Let's Encrypt expired on 29 Mar 2024, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
127 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| lpfs.net | Look-alike characters | 26 Oct 2026 | Checking… | Report → |
| ipfs.net.cn | Other extension | 8 Nov 2026 | Checking… | Report → |
| ipfs.berlin | Other extension | 6 Nov 2026 | Checking… | Report → |
| pifs.uk | Typo | 19 Oct 2026 | Checking… | Report → |
| ipfs.family | Other extension | 5 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is ipfs.tech’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| United States | 18.9% | — | — | — |
| India | 11.4% | — | — | — |
| China | 8% | — | — | — |
| Hong Kong SAR China | 7% | — | — | — |
| Taiwan | 5.1% | — | — | — |
Every IP address ipfs.tech resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| ipfs.tech | 109.61.83.242 | 60 |
| Host | IPv6 address | TTL |
|---|---|---|
| ipfs.tech | 2400:52e0:1e00::1080:1 | 60 |
| Host | Mail server | TTL |
|---|---|---|
| ipfs.tech | 1 aspmx.l.google.com | 3600 |
| ipfs.tech | 5 alt1.aspmx.l.google.com | 3600 |
| ipfs.tech | 5 alt2.aspmx.l.google.com | 3600 |
| ipfs.tech | 10 alt3.aspmx.l.google.com | 3600 |
| ipfs.tech | 10 alt4.aspmx.l.google.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| ipfs.tech | ns1.dnsimple.com | 3600 |
| ipfs.tech | ns2.dnsimple.com | 3600 |
| ipfs.tech | ns3.dnsimple.com | 3600 |
| ipfs.tech | ns4.dnsimple.com | 3600 |
| Host | Text | TTL |
|---|---|---|
| ipfs.tech | "ALIAS for a5b954c3f3a999966767.b-cdn.net" | 60 |
| ipfs.tech | "google-site-verification=cgzVToIa5A2CFs20pqsXzCRN2WEEVndbszvnqdzcIdg" | 60 |
| ipfs.tech | "google-site-verification=Dmx7_9PHmZ3beNgqQ9CCxh0tzi-fdsoqNCj9C8C-ezU" | 60 |
| ipfs.tech | "v=spf1 a include:_spf.google.com include:spf.mandrillapp.com include:servers.mcsv.net ~all" | 60 |
| Host | Start of authority | TTL |
|---|---|---|
| ipfs.tech | ns1.dnsimple.com admin.dnsimple.com 1658865334 86400 7200 604800 300 | 3600 |
No reviews yet. Used ipfs.tech? 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.
ipfs.tech has no community safety rating yet. Its SSL certificate expired on 29 Mar 2024. See Security →
ipfs.tech is registered through CSC Corporate Domains Inc. The public WHOIS record shows the registrant’s details. See WHOIS →
The registration expired on 28 May 2025. See Overview →
ipfs.tech was registered on 27 May 2020, making it 6 years old. See Overview →
ipfs.tech is served from 1 IP address, mainly on AS60068 DataCamp Limited in Japan. See Hosting →
Raw registry data for ipfs.tech. May be redacted by privacy services.
Domain Name: IPFS.TECH Registry Domain ID: D187706284-CNIC Registrar WHOIS Server: whois.corporatedomains.com Registrar URL: Updated Date: 2023-08-31T16:52:51.0Z Creation Date: 2020-05-28T00:56:45.0Z Registry Expiry Date: 2025-05-28T23:59:59.0Z Registrar: CSC Corporate Domains Inc. Registrar IANA ID: 299 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registrant Organization: Protocol Labs, Inc. Registrant State/Province: DE Registrant Country: US Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Name Server: NS1.DNSIMPLE.COM Name Server: NS2.DNSIMPLE.COM Name Server: NS3.DNSIMPLE.COM Name Server: NS4.DNSIMPLE.COM DNSSEC: unsigned Billing Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.3026365400 URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2024-01-02T05:56:43.0Z <<< For more information on Whois status codes, please visit https://icann.org/epp >>> IMPORTANT INFORMATION ABOUT THE DEPLOYMENT OF RDAP: please visit https://www.centralnic.com/support/rdap <<< The Whois and RDAP services are provided by CentralNic, and contain information pertaining to Internet domain names registered by our our customers. By using this service you are agreeing (1) not to use any information presented here for any purpose other than determining ownership of domain names, (2) not to store or reproduce this data in any way, (3) not to use any high-volume, automated, electronic processes to obtain data from this service. Abuse of this service is monitored and actions in contravention of these terms will result in being permanently blacklisted. All data is (c) CentralNic Ltd (https://www.centralnic.com) Access to the Whois and RDAP services is rate limited. For more information, visit https://registrar-console.centralnic.com/pub/whois_guidance.
The first response from http://www.ipfs.tech, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with ipfs.tech. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.