trihard.win is registered with whois.nic.win. 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.
0 of 5 protections set up
No SPF record: any server can send mail that claims to come from this domain.
—No 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.
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 trihard.win. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
19 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| trihard.app | Other extension | 20 Oct 2026 | Checking… | Report → |
| trihard.club | Other extension | 2 Oct 2026 | Checking… | Report → |
| tribard.ai | Typo | 9 Oct 2026 | Checking… | Report → |
| triard.ru | Typo | 3 Oct 2026 | Checking… | Report → |
| triard.tech | Typo | 3 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is trihard.win’s name taken on other extensions?
No reviews yet. Used trihard.win? 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.
trihard.win has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
trihard.win is registered through whois.nic.win. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
Raw registry data for trihard.win. May be redacted by privacy services.
No Data Found URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2026-11-02T01:42:28Z <<< For more information on Whois status codes, please visit https://icann.org/epp The Service is provided so that you may look up certain information in relation to domain names that we store in our database. Use of the Service is subject to our policies, in particular you should familiarise yourself with our Acceptable Use Policy and our Privacy Policy. The information provided by this Service is 'as is' and we make no guarantee of it its accuracy. You agree that by your use of the Service you will not use the information provided by us in a way which is: * inconsistent with any applicable laws, * inconsistent with any policy issued by us, * to generate, distribute, or facilitate unsolicited mass email, promotions, advertisings or other solicitations, or * to enable high volume, automated, electronic processes that apply to the Service. You acknowledge that: * a response from the Service that a domain name is 'available', does not guarantee that is able to be registered, * we may restrict, suspend or terminate your access to the Service at any time, and * the copying, compilation, repackaging, dissemination or other use of the information provided by the Service is not permitted, without our express written consent. This information has been prepared and published in order to represent administrative and technical management of the TLD. We may discontinue or amend any part or the whole of these Terms of Service from time to time at our absolute discretion.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with trihard.win. 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.
We couldn't find an IP address for trihard.win's web or mail servers to check.
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 2 Nov 2026.