39160.channel was registered on 23 Aug 2014 and is hosted on AS59371 in Hong Kong. Its SSL certificate from Let's Encrypt expired on 4 Dec 2025, and the site does not support HTTP/3.
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.
Internet standards that make a site faster and safer.
70 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| 39106.my | Typo | 7 Oct 2026 | Active website | Report → |
| 39610.ch | Typo | 20 Sept 2026 | No website | Report → |
| 39610.co | Typo | 27 Aug 2026 | Active website | Report → |
| 391600.vip | Extra letter | 4 Oct 2026 | Active website | Report → |
| 3910.fun | Typo | 7 Nov 2026 | No website | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is 39160.channel’s name taken on other extensions?
Every IP address 39160.channel resolves to, and where it's hosted.
Other domains served from 46.149.207.118. Normal for shared hosting and CDNs.
No reviews yet. Used 39160.channel? 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.
39160.channel has no community safety rating yet. Its SSL certificate expired on 4 Dec 2025. See Security →
39160.channel was registered on 23 Aug 2014, making it 12 years old. See Overview →
39160.channel is served from 2 IP addresses, mainly on AS59371 in Hong Kong. See Hosting →
Raw registry data for 39160.channel. 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: CHANNEL organisation: Charleston Road Registry Inc. address: 1600 Amphitheatre Parkway address: Mountain View CA 94043 address: United States of America (the) contact: administrative name: TLD Admin organisation: Google Inc. address: 111 8th Avenue address: New York NY 10011 address: United States of America (the) phone: +1 404 978 8419 fax-no: +1 650 492 5631 e-mail: iana-contact@google.com contact: technical name: TLD Engineering organisation: Google Inc. address: 76 Ninth Avenue, 4th Floor address: New York NY 10011 address: United States of America (the) phone: +1 404 978 8419 fax-no: +1 650 492 5631 e-mail: crr-tech@google.com nserver: NS-TLD1.CHARLESTONROADREGISTRY.COM 2001:4860:4802:32:0:0:0:69 216.239.32.105 nserver: NS-TLD2.CHARLESTONROADREGISTRY.COM 2001:4860:4802:34:0:0:0:69 216.239.34.105 nserver: NS-TLD3.CHARLESTONROADREGISTRY.COM 2001:4860:4802:36:0:0:0:69 216.239.36.105 nserver: NS-TLD4.CHARLESTONROADREGISTRY.COM 2001:4860:4802:38:0:0:0:69 216.239.38.105 nserver: NS-TLD5.CHARLESTONROADREGISTRY.COM 2001:4860:4805:0:0:0:0:69 216.239.60.105 ds-rdata: 37051 8 2 ad6600649ad83f822ceea5731ea43cb0c560636908219fe59bc5b0d0e5757840 whois: status: ACTIVE remarks: Registration information: https://www.registry.google created: 2014-08-23 changed: 2025-04-11 source: IANA
The first response from http://www.39160.channel, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with 39160.channel. 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 39160.channel'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 17 Nov 2026.