Identity
14
F
netease.com
Posture Score: 47/100
Scanned May 27, 2026 at 6:44 AM UTC
Attack Surface
83
Reputation
43
Identity Findings
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.netease.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@netease.com").
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: No DMARC record published (required since Feb 2024)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
FCrDNS failure: no PTR for 103.129.252.65 (yeahmx00.mxmail.netease.com)
The IP 103.129.252.65 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS failure: no PTR for 103.129.252.65 (yeahmx01.mxmail.netease.com)
The IP 103.129.252.65 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
Inconsistent SOA serials across nameservers
Nameservers return different SOA serial numbers, indicating zone transfer lag or failure.
💡 Verify zone transfers are working correctly between primary and secondary nameservers.
SOA serial mismatch across nameservers
Nameservers report different SOA serial numbers, indicating zone transfer lag or failure.
💡 Check zone transfer configuration and ensure all secondary nameservers are receiving updates.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.netease.com
No PTR record for MX IP: 103.129.252.65
The IP 103.129.252.65 (for yeahmx00.mxmail.netease.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 103.129.252.65
The IP 103.129.252.65 (for yeahmx01.mxmail.netease.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.netease.com/.well-known/mta-sts.txt
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
No TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@netease.com").
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
No PTR record for IPv6 address: 240e:938:a07:6:0:14:20:13
The IPv6 address 240e:938:a07:6:0:14:20:13 for yeahmx00.mxmail.netease.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 240e:938:a07:6:0:14:203:54
The IPv6 address 240e:938:a07:6:0:14:203:54 for yeahmx00.mxmail.netease.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 240e:938:a07:6:0:14:20:13
The IPv6 address 240e:938:a07:6:0:14:20:13 for yeahmx01.mxmail.netease.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 240e:938:a07:6:0:14:203:54
The IPv6 address 240e:938:a07:6:0:14:203:54 for yeahmx01.mxmail.netease.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
Shared IP 103.129.252.65 used by multiple MX servers
The IP 103.129.252.65 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (36 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
REQUIRETLS not advertised
The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on yeahmx00.mxmail.netease.com
Detected open mail-related ports: 25, 465, 587
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
MX IPs span 2 different /16 networks, providing good diversity.
SOA record parameters
Serial: 20835696, Refresh: 7200s, Retry: 1800s, Expire: 1209600s, Min TTL: 60s
Attack Surface Findings
Non-routable IPv4 in public DNS: remote.netease.com → 10.246.3.57
The subdomain remote.netease.com resolves to non-routable IP 10.246.3.57, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
DNS ANY query returns 14 record(s)
The DNS server responds to ANY queries with 14 record(s). The low record count limits amplification risk, but ANY responses still aid reconnaissance.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
15 subdomain(s) discovered for netease.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for netease.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Listed on dnsbl-3.uceprotect.net
103.129.252.65 (yeahmx01.mxmail.netease.com) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
103.129.252.65 (yeahmx01.mxmail.netease.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
154.18.236.100 (yeahmx01.mxmail.netease.com) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
SMTP banner mismatch: yeah.net
The SMTP banner identifies as 'yeah.net' but the MX hostname is 'yeahmx01.mxmail.netease.com' and PTR resolves to 'sgmail100.mail.163.com'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (yeahmx01.mxmail.netease.com).
Missing Strict-Transport-Security on netease.com
The Strict-Transport-Security header is not set on https://netease.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
security.txt present
Found security.txt at https://netease.com/.well-known/security.txt.
TLS certificate valid for 251 days
Certificate for netease.com expires on 2027-02-03.
Certificate issued by vTrus OV SSL CA G2
The certificate for netease.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for netease.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for netease.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for netease.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on netease.com.
Domain valid for 681 days
Domain netease.com expires on 2028-04-08.
Domain transfer and delete locks enabled
Domain netease.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for netease.com do not match known disposable email provider patterns.
Domain is 10275 days old
Domain netease.com was registered 1998-04-09.
No wildcard MX records
No wildcard MX records detected for netease.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (yeahmx01.mxmail.netease.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
Could not connect to webmail.netease.com
HTTPS request to https://webmail.netease.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Information Technology (Shanghai) Co., Ltd. | Created: 1998-04-09 | Expires: 2028-04-08 | Updated: 2026-01-08
WHOIS privacy protection not detected
Domain netease.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: netaese.com (has MX!), neteaes.com (has MX!), betease.com (has MX!), jetease.com (has MX!), metease.com (has MX!)
18 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 18. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy missing
⚠️ DMARC policy is missing. Even with SPF configured, you lack the policy layer that tells receiving servers what to do with authentication failures.
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature missing
→
DMARC Policy
DMARC policy missing
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Mail Server Identity: yeahmx00.mxmail.netease.com
PTR record proves mail server legitimacy
MX: yeahmx00.mxmail.netease.com
Mail server at 103.129.252.65
→
PTR Record
No PTR record
⚠️ Mail server yeahmx00.mxmail.netease.com (103.129.252.65) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: yeahmx01.mxmail.netease.com
PTR record proves mail server legitimacy
MX: yeahmx01.mxmail.netease.com
Mail server at 154.18.236.100
→
PTR Record
Reverse DNS: sgmail100.mail.163.com
Mail Server Reputation: yeahmx00.mxmail.netease.com
RBL check ensures server is not blacklisted
MX: yeahmx00.mxmail.netease.com
Mail server at 103.129.252.65
→
RBL Status
Not blacklisted
Mail Server Reputation: yeahmx01.mxmail.netease.com
RBL check ensures server is not blacklisted
MX: yeahmx01.mxmail.netease.com
Mail server at 154.18.236.100
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✗
BIMI Record
✗
CAA Records
✗
DNSSEC
✗
MTA-STS
✗
TLS-RPT
✗
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/netease.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan netease.com Again