Identity
0
F
oppomobile.com
Posture Score: 29/100
Scanned May 30, 2026 at 7:55 AM UTC
Attack Surface
0
Reputation
88
Identity Findings
No SPF record found
The domain has no SPF record, allowing anyone to send email as this domain.
💡 Publish an SPF TXT record (e.g. "v=spf1 include:_spf.google.com -all").
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.oppomobile.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@oppomobile.com").
MX record points to IP address: 218.247.51.97
MX records must point to hostnames, not IP addresses (RFC 5321).
💡 Replace the IP address with a hostname that resolves to the mail server.
MX record points to IP address: 218.247.51.98
MX records must point to hostnames, not IP addresses (RFC 5321).
💡 Replace the IP address with a hostname that resolves to the mail server.
MX record points to IP address: 218.247.51.99
MX records must point to hostnames, not IP addresses (RFC 5321).
💡 Replace the IP address with a hostname that resolves to the mail server.
MX record points to IP address: 218.247.51.100
MX records must point to hostnames, not IP addresses (RFC 5321).
💡 Replace the IP address with a hostname that resolves to the mail server.
MX record points to IP address: 218.247.51.101
MX records must point to hostnames, not IP addresses (RFC 5321).
💡 Replace the IP address with a hostname that resolves to the mail server.
MX record points to IP address: 218.247.51.102
MX records must point to hostnames, not IP addresses (RFC 5321).
💡 Replace the IP address with a hostname that resolves to the mail server.
MX record points to IP address: 218.247.51.103
MX records must point to hostnames, not IP addresses (RFC 5321).
💡 Replace the IP address with a hostname that resolves to the mail server.
MX record points to IP address: 218.247.51.104
MX records must point to hostnames, not IP addresses (RFC 5321).
💡 Replace the IP address with a hostname that resolves to the mail server.
MX record points to IP address: 218.247.51.105
MX records must point to hostnames, not IP addresses (RFC 5321).
💡 Replace the IP address with a hostname that resolves to the mail server.
MX record points to IP address: 218.247.51.106
MX records must point to hostnames, not IP addresses (RFC 5321).
💡 Replace the IP address with a hostname that resolves to the mail server.
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.
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: Neither SPF nor DKIM is configured (at least one required); No DMARC record published (required since Feb 2024); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
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.oppomobile.com
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.oppomobile.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@oppomobile.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.
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.
Mail server port configuration is acceptable
No concerning port exposure detected.
FCrDNS checks passed
All MX server IPs have valid forward-confirmed reverse DNS.
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.
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.
SOA record parameters
Serial: 1778065413, Refresh: 3600s, Retry: 180s, Expire: 1209600s, Min TTL: 180s
Attack Surface Findings
Dangling MX: 218.247.51.103 does not resolve
The MX record points to 218.247.51.103 which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to 218.247.51.103 or update it to your current mail provider.
Dangling MX: 218.247.51.97 does not resolve
The MX record points to 218.247.51.97 which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to 218.247.51.97 or update it to your current mail provider.
Dangling MX: 218.247.51.100 does not resolve
The MX record points to 218.247.51.100 which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to 218.247.51.100 or update it to your current mail provider.
Dangling MX: 218.247.51.106 does not resolve
The MX record points to 218.247.51.106 which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to 218.247.51.106 or update it to your current mail provider.
Dangling MX: 218.247.51.99 does not resolve
The MX record points to 218.247.51.99 which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to 218.247.51.99 or update it to your current mail provider.
Dangling MX: 218.247.51.104 does not resolve
The MX record points to 218.247.51.104 which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to 218.247.51.104 or update it to your current mail provider.
Dangling MX: 218.247.51.98 does not resolve
The MX record points to 218.247.51.98 which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to 218.247.51.98 or update it to your current mail provider.
Dangling MX: 218.247.51.101 does not resolve
The MX record points to 218.247.51.101 which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to 218.247.51.101 or update it to your current mail provider.
Dangling MX: 218.247.51.105 does not resolve
The MX record points to 218.247.51.105 which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to 218.247.51.105 or update it to your current mail provider.
Dangling MX: 218.247.51.102 does not resolve
The MX record points to 218.247.51.102 which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to 218.247.51.102 or update it to your current mail provider.
NSEC records enable zone walking
The domain uses NSEC records for DNSSEC authenticated denial of existence. NSEC records can be walked to enumerate all names in the zone, effectively disclosing the entire zone contents.
💡 Switch from NSEC to NSEC3 with opt-out to prevent zone enumeration. Use NSEC3 with a random salt and sufficient iterations.
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
DNS ANY query returns 23 record(s)
The DNS server responds to ANY queries with 23 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
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.
No subdomain takeover risks detected
All checked subdomains have valid, responsive targets.
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.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
2 subdomain(s) discovered for oppomobile.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 oppomobile.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain oppomobile.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Missing Strict-Transport-Security on oppomobile.com
The Strict-Transport-Security header is not set on https://oppomobile.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
security.txt present
Found security.txt at https://oppomobile.com/.well-known/security.txt.
TLS certificate valid for 52 days
Certificate for oppomobile.com expires on 2026-07-21.
Certificate issued by GeoTrust G2 TLS CN RSA4096 SHA256 2022 CA1
The certificate for oppomobile.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for oppomobile.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for oppomobile.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for oppomobile.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on oppomobile.com.
Domain valid for 843 days
Domain oppomobile.com expires on 2028-09-20.
No disposable email provider MX records
MX records for oppomobile.com do not match known disposable email provider patterns.
Domain is 6827 days old
Domain oppomobile.com was registered 2007-09-20.
No wildcard MX records
No wildcard MX records detected for oppomobile.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 (218.247.51.97) uses with cipher 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.
No abuse contacts resolved
Could not resolve abuse contact information for MX IPs via abusix.org.
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.oppomobile.com
HTTPS request to https://webmail.oppomobile.com failed or timed out.
WHOIS registration data
Registrar: Alibaba Cloud Computing (Beijing) Co., Ltd. | Created: 2007-09-20 | Expires: 2028-09-20 | Updated: 2025-11-12
WHOIS privacy protection not detected
Domain oppomobile.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: oppmobile.com (has MX!)
1 registered lookalike domain(s) that could be used for phishing against your brand. 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 missing
→
DMARC Policy
DMARC policy missing
⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.
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: 218.247.51.97
PTR record proves mail server legitimacy
MX: 218.247.51.97
Mail server at 218.247.51.97
→
PTR Record
No PTR record
⚠️ Mail server 218.247.51.97 (218.247.51.97) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: 218.247.51.98
PTR record proves mail server legitimacy
MX: 218.247.51.98
Mail server at 218.247.51.98
→
PTR Record
No PTR record
⚠️ Mail server 218.247.51.98 (218.247.51.98) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: 218.247.51.99
PTR record proves mail server legitimacy
MX: 218.247.51.99
Mail server at 218.247.51.99
→
PTR Record
No PTR record
⚠️ Mail server 218.247.51.99 (218.247.51.99) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: 218.247.51.100
PTR record proves mail server legitimacy
MX: 218.247.51.100
Mail server at 218.247.51.100
→
PTR Record
No PTR record
⚠️ Mail server 218.247.51.100 (218.247.51.100) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: 218.247.51.101
PTR record proves mail server legitimacy
MX: 218.247.51.101
Mail server at 218.247.51.101
→
PTR Record
No PTR record
⚠️ Mail server 218.247.51.101 (218.247.51.101) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: 218.247.51.102
PTR record proves mail server legitimacy
MX: 218.247.51.102
Mail server at 218.247.51.102
→
PTR Record
No PTR record
⚠️ Mail server 218.247.51.102 (218.247.51.102) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: 218.247.51.103
PTR record proves mail server legitimacy
MX: 218.247.51.103
Mail server at 218.247.51.103
→
PTR Record
No PTR record
⚠️ Mail server 218.247.51.103 (218.247.51.103) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: 218.247.51.104
PTR record proves mail server legitimacy
MX: 218.247.51.104
Mail server at 218.247.51.104
→
PTR Record
No PTR record
⚠️ Mail server 218.247.51.104 (218.247.51.104) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: 218.247.51.105
PTR record proves mail server legitimacy
MX: 218.247.51.105
Mail server at 218.247.51.105
→
PTR Record
No PTR record
⚠️ Mail server 218.247.51.105 (218.247.51.105) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: 218.247.51.106
PTR record proves mail server legitimacy
MX: 218.247.51.106
Mail server at 218.247.51.106
→
PTR Record
No PTR record
⚠️ Mail server 218.247.51.106 (218.247.51.106) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: 218.247.51.97
RBL check ensures server is not blacklisted
MX: 218.247.51.97
Mail server at 218.247.51.97
→
RBL Status
Not blacklisted
Mail Server Reputation: 218.247.51.98
RBL check ensures server is not blacklisted
MX: 218.247.51.98
Mail server at 218.247.51.98
→
RBL Status
Not blacklisted
Mail Server Reputation: 218.247.51.99
RBL check ensures server is not blacklisted
MX: 218.247.51.99
Mail server at 218.247.51.99
→
RBL Status
Not blacklisted
Mail Server Reputation: 218.247.51.100
RBL check ensures server is not blacklisted
MX: 218.247.51.100
Mail server at 218.247.51.100
→
RBL Status
Not blacklisted
Mail Server Reputation: 218.247.51.101
RBL check ensures server is not blacklisted
MX: 218.247.51.101
Mail server at 218.247.51.101
→
RBL Status
Not blacklisted
Mail Server Reputation: 218.247.51.102
RBL check ensures server is not blacklisted
MX: 218.247.51.102
Mail server at 218.247.51.102
→
RBL Status
Not blacklisted
Mail Server Reputation: 218.247.51.103
RBL check ensures server is not blacklisted
MX: 218.247.51.103
Mail server at 218.247.51.103
→
RBL Status
Not blacklisted
Mail Server Reputation: 218.247.51.104
RBL check ensures server is not blacklisted
MX: 218.247.51.104
Mail server at 218.247.51.104
→
RBL Status
Not blacklisted
Mail Server Reputation: 218.247.51.105
RBL check ensures server is not blacklisted
MX: 218.247.51.105
Mail server at 218.247.51.105
→
RBL Status
Not blacklisted
Mail Server Reputation: 218.247.51.106
RBL check ensures server is not blacklisted
MX: 218.247.51.106
Mail server at 218.247.51.106
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
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
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/oppomobile.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan oppomobile.com Again