tryshift.info was registered on 25 Jun 2001. We couldn't read an SSL certificate for it when we last analysed it.
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.
We couldn't read an SSL certificate on port 443 when we last analysed tryshift.info. Refresh the analysis to check again.
39 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| tryshift.dev | Other extension | 15 Oct 2026 | Checking… | Report → |
| tryshift.tech | Other extension | 10 Oct 2026 | Checking… | Report → |
| tryshift.uk | Other extension | 18 Sept 2026 | Checking… | Report → |
| tryshift.online | Other extension | 22 Aug 2026 | Checking… | Report → |
| fryshift.xyz | Typo | 6 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is tryshift.info’s name taken on other extensions?
| Host | Mail server | TTL |
|---|---|---|
| tryshift.info | 1 smtp.google.com | 600 |
| Host | Name server | TTL |
|---|---|---|
| tryshift.info | curitiba.ns.porkbun.com | 21600 |
| tryshift.info | fortaleza.ns.porkbun.com | 21600 |
| tryshift.info | maceio.ns.porkbun.com | 21600 |
| tryshift.info | salvador.ns.porkbun.com | 21600 |
| Host | Text | TTL |
|---|---|---|
| tryshift.info | "v=spf1 include:_spf.google.com ~all" | 600 |
| Host | Start of authority | TTL |
|---|---|---|
| tryshift.info | curitiba.ns.porkbun.com dns.cloudflare.com 2382251429 10000 2400 604800 1800 | 1800 |
No reviews yet. Used tryshift.info? 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.
tryshift.info has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
tryshift.info was registered on 25 Jun 2001, making it 25 years old. See Overview →
Raw registry data for tryshift.info. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: domain: INFO organisation: Identity Digital Limited address: c/o Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) contact: administrative name: Vice President, Engineering organisation: Identity Digital Limited address: c/o Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) phone: +1.425.298.2200 fax-no: +1.425.671.0020 e-mail: [email protected] contact: technical name: Senior Director, DNS Infrastructure Group organisation: Identity Digital Limited address: c/o Identity Digital Inc. address: 10500 NE 8th Street, Suite 750 address: Bellevue WA 98004 address: United States of America (the) phone: +1.425.298.2200 fax-no: +1.425.671.0020 e-mail: [email protected] nserver: A0.INFO.AFILIAS-NST.INFO 199.254.31.1 2001:500:19:0:0:0:0:1 nserver: A2.INFO.AFILIAS-NST.INFO 199.249.113.1 2001:500:41:0:0:0:0:1 nserver: B0.INFO.AFILIAS-NST.ORG 199.254.48.1 2001:500:1a:0:0:0:0:1 nserver: B2.INFO.AFILIAS-NST.ORG 199.249.121.1 2001:500:49:0:0:0:0:1 nserver: C0.INFO.AFILIAS-NST.INFO 199.254.49.1 2001:500:1b:0:0:0:0:1 nserver: D0.INFO.AFILIAS-NST.ORG 199.254.50.1 2001:500:1c:0:0:0:0:1 ds-rdata: 5104 8 2 1af7548a8d3e2950c20303757df9390c26cfa39e26c8b6a8f6c8b1e72dd8f744 whois: status: ACTIVE remarks: Registration information: https://www.identity.digital/ created: 2001-06-26 changed: 2025-09-04 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with tryshift.info. 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.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.