Identity
0
F
163.com
Posture Score: 41/100
Scanned May 27, 2026 at 9:28 PM UTC
Score History
Attack Surface
80
Reputation
43
Identity Findings
No NS records found
No nameserver records could be retrieved for this domain.
💡 Ensure NS records are properly configured at your registrar and in your zone file.
Subdomains have no DMARC enforcement
No sp= tag set and p=none. Subdomains inherit the monitoring-only policy, leaving them open to spoofing.
💡 Add sp=reject (or sp=quarantine) to your DMARC record to protect subdomains.
FCrDNS failure: no PTR for 103.129.252.43 (163mx02.mxmail.netease.com)
The IP 103.129.252.43 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.43 (163mx03.mxmail.netease.com)
The IP 103.129.252.43 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.43 (163mx00.mxmail.netease.com)
The IP 103.129.252.43 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.43 (163mx01.mxmail.netease.com)
The IP 103.129.252.43 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.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
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.163.com
DMARC policy is monitoring-only (p=none)
The p=none policy only monitors; it does not instruct receivers to quarantine or reject unauthenticated mail.
💡 Upgrade to p=quarantine or p=reject after reviewing aggregate reports.
No DMARC aggregate report URI (rua=)
Without rua=, you will not receive aggregate reports about authentication results.
💡 Add rua=mailto:dmarc-reports@163.com to your DMARC record.
No PTR record for MX IP: 103.129.252.43
The IP 103.129.252.43 (for 163mx02.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.43
The IP 103.129.252.43 (for 163mx03.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.43
The IP 103.129.252.43 (for 163mx00.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.43
The IP 103.129.252.43 (for 163mx01.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.163.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@163.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.
Shared IP 154.18.236.98 used by multiple MX servers
The IP 154.18.236.98 is shared across 3 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 103.129.252.43 used by multiple MX servers
The IP 103.129.252.43 is shared across 4 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.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
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.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
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 163mx02.mxmail.netease.com
Detected open mail-related ports: 25, 465, 587
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
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: 20297451, Refresh: 7200s, Retry: 1800s, Expire: 1209600s, Min TTL: 60s
Attack Surface Findings
Microsoft Autodiscover accessible without authentication
The Autodiscover endpoint at https://autodiscover.163.com/autodiscover/autodiscover.xml returns configuration data without requiring authentication. This exposes email server details to unauthenticated users.
💡 Configure the Autodiscover endpoint to require authentication before returning configuration data.
DNS ANY query returns 28 record(s)
The DNS server responds to ANY queries with 28 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
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.
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 internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
9 subdomain(s) discovered for 163.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 163.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Listed on dnsbl-3.uceprotect.net
154.18.236.98 (163mx01.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-3.uceprotect.net
103.129.252.43 (163mx01.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.43 (163mx01.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.
SMTP banner mismatch: 163.com
The SMTP banner identifies as '163.com' but the MX hostname is '163mx02.mxmail.netease.com' and PTR resolves to 'sgmail98.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 (163mx02.mxmail.netease.com).
Missing Strict-Transport-Security on 163.com
The Strict-Transport-Security header is not set on https://163.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://163.com/.well-known/security.txt.
TLS certificate valid for 150 days
Certificate for 163.com expires on 2026-10-24.
Certificate issued by GeoTrust G2 TLS CN RSA4096 SHA256 2022 CA1
The certificate for 163.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for 163.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for 163.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for 163.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on 163.com.
Domain valid for 474 days
Domain 163.com expires on 2027-09-14.
Domain transfer and delete locks enabled
Domain 163.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for 163.com do not match known disposable email provider patterns.
Domain is 10481 days old
Domain 163.com was registered 1997-09-15.
No wildcard MX records
No wildcard MX records detected for 163.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (163mx02.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.163.com
HTTPS request to https://webmail.163.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Information Technology (Shanghai) Co., Ltd. | Created: 1997-09-15 | Expires: 2027-09-14 | Updated: 2023-09-22
WHOIS privacy protection not detected
Domain 163.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: 613.com (has MX!), 163.net (has MX!), 163.xyz (has MX!), 1s63.com (has MX!), 63.com
17 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 17. 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: none
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: none
⚠️ 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: 163mx02.mxmail.netease.com
PTR record proves mail server legitimacy
MX: 163mx02.mxmail.netease.com
Mail server at 103.129.252.43
→
PTR Record
No PTR record
⚠️ Mail server 163mx02.mxmail.netease.com (103.129.252.43) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: 163mx03.mxmail.netease.com
PTR record proves mail server legitimacy
MX: 163mx03.mxmail.netease.com
Mail server at 154.18.236.98
→
PTR Record
Reverse DNS: sgmail98.mail.163.com
Mail Server Identity: 163mx00.mxmail.netease.com
PTR record proves mail server legitimacy
MX: 163mx00.mxmail.netease.com
Mail server at 103.129.252.43
→
PTR Record
No PTR record
⚠️ Mail server 163mx00.mxmail.netease.com (103.129.252.43) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: 163mx01.mxmail.netease.com
PTR record proves mail server legitimacy
MX: 163mx01.mxmail.netease.com
Mail server at 154.18.236.98
→
PTR Record
Reverse DNS: sgmail98.mail.163.com
Mail Server Reputation: 163mx02.mxmail.netease.com
RBL check ensures server is not blacklisted
MX: 163mx02.mxmail.netease.com
Mail server at 103.129.252.43
→
RBL Status
Not blacklisted
Mail Server Reputation: 163mx03.mxmail.netease.com
RBL check ensures server is not blacklisted
MX: 163mx03.mxmail.netease.com
Mail server at 154.18.236.98
→
RBL Status
Not blacklisted
Mail Server Reputation: 163mx00.mxmail.netease.com
RBL check ensures server is not blacklisted
MX: 163mx00.mxmail.netease.com
Mail server at 103.129.252.43
→
RBL Status
Not blacklisted
Mail Server Reputation: 163mx01.mxmail.netease.com
RBL check ensures server is not blacklisted
MX: 163mx01.mxmail.netease.com
Mail server at 154.18.236.98
→
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/163.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan 163.com Again