netease.com was registered with whois.verisign-grs.com on 9 Apr 1998 and is hosted on AS58461 No.288 Fu-chun Road in China. We couldn't read an SSL certificate for it when we last analysed it. WOT's community rates its safety poor (32/100).
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 netease.com. Refresh the analysis to check again.
Is netease.com’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| China | 39.6% | 1,049,747 | 100% | 0% |
| Taiwan | 19.3% | 511,649 | 1.5% | 98.5% |
| Indonesia | 11.2% | 296,688 | 0.7% | 99.3% |
| United States | 6.4% | 168,444 | 55.2% | 44.8% |
| Hong Kong SAR China | 3.6% | 95,302 | 78.1% | 21.9% |
Every IP address netease.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| netease.com | 115.236.118.54 | 600 |
| Host | Mail server | TTL |
|---|---|---|
| netease.com | 10 yeahmx01.mxmail.netease.com | 18000 |
| netease.com | 50 yeahmx00.mxmail.netease.com | 18000 |
| Host | Name server | TTL |
|---|---|---|
| netease.com | ns1.nease.net | 21600 |
| netease.com | ns2.166.com | 21600 |
| netease.com | ns3.nease.net | 21600 |
| netease.com | ns4.nease.net | 21600 |
| netease.com | ns5.nease.net | 21600 |
| netease.com | ns6.nease.net | 21600 |
| netease.com | ns8.166.com | 21600 |
| Host | Text | TTL |
|---|---|---|
| netease.com | "0hz8zn8jpkr3vffgll8hnd6j873bzvsg" | 18000 |
| netease.com | "9300w82jh2zwd2r8yccyqxpnyq7pljw5" | 18000 |
| netease.com | "google-site-verification=GgpoPB-rR81FZEft1rcZVIxw0DyOEJXcYecYFeOq3SQ" | 18000 |
| netease.com | "v=spf1 include:spf.mail.163.com -all" | 18000 |
| Host | Start of authority | TTL |
|---|---|---|
| netease.com | ns4.nease.net admin.nease.net 20530334 7200 1800 1209600 60 | 21600 |
No reviews yet. Used netease.com? 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.
WOT's community rates netease.com poor for safety (32/100). We couldn't read an SSL certificate on it when we last analysed it. See Security →
netease.com is registered through whois.verisign-grs.com. See WHOIS →
The registration expires on 8 Apr 2028 — in 17 months. See Overview →
netease.com was registered on 9 Apr 1998, making it 28 years old. See Overview →
netease.com is served from 1 IP address, mainly on AS58461 No.288 Fu-chun Road in China. See Hosting →
Raw registry data for netease.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"1088312_DOMAIN_COM-VRSN","ldhName":"NETEASE.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/NETEASE.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/NETEASE.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.markmonitor.com\/rdap\/domain\/NETEASE.COM","rel":"related","href":"https:\/\/rdap.markmonitor.com\/rdap\/domain\/NETEASE.COM","type":"application\/rdap+json"}],"status":["client delete prohibited","client transfer prohibited","client update prohibited","server delete prohibited","server transfer prohibited","server update prohibited"],"entities":[{"objectClassName":"entity","handle":"3838","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"3838"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","MarkMonitor Information Technology (Shanghai) Co., Ltd."]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+1.2083895740"],["email",{},"text","[email protected]"]]]}]}],"events":[{"eventAction":"registration","eventDate":"1998-04-09T04:00:00Z"},{"eventAction":"expiration","eventDate":"2028-04-08T04:00:00Z"},{"eventAction":"last changed","eventDate":"2023-09-22T06:35:51Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-10-27T02:23:29Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS1.NEASE.NET"},{"objectClassName":"nameserver","ldhName":"NS2.166.COM"},{"objectClassName":"nameserver","ldhName":"NS3.NEASE.NET"},{"objectClassName":"nameserver","ldhName":"NS4.NEASE.NET"},{"objectClassName":"nameserver","ldhName":"NS5.NEASE.NET"},{"objectClassName":"nameserver","ldhName":"NS6.NEASE.NET"},{"objectClassName":"nameserver","ldhName":"NS8.166.COM"}],"rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_0","icann_rdap_response_profile_0"],"notices":[{"title":"Terms of Use","description":["Service subject to Terms of Use."],"links":[{"href":"https:\/\/www.verisign.com\/domain-names\/registration-data-access-protocol\/terms-service\/index.xhtml","type":"text\/html"}]},{"title":"Status Codes","description":["For more information on domain status codes, please visit https:\/\/icann.org\/epp"],"links":[{"href":"https:\/\/icann.org\/epp","type":"text\/html"}]},{"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https:\/\/icann.org\/wicf"],"links":[{"href":"https:\/\/icann.org\/wicf","type":"text\/html"}]}]}The first response from http://www.netease.com, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with netease.com. 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.