Identity
56
D
ifeng.com
Posture Score: 67/100
Scanned May 29, 2026 at 10:45 AM UTC
Attack Surface
79
Reputation
66
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.
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.ifeng.com
No DMARC aggregate report URI (rua=)
Without rua=, you will not receive aggregate reports about authentication results.
💡 Add rua=mailto:dmarc-reports@ifeng.com to your DMARC record.
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.ifeng.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@ifeng.com").
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (113 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.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
MX records are valid
All MX records are properly configured.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
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.
IPv6 readiness is good
IPv6 records are present and properly configured.
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 ifeng-com.mail.protection.partner.outlook.cn
Detected open mail-related ports: 25
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
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 1779869851, Refresh: 3600s, Retry: 180s, Expire: 1209600s, Min TTL: 180s
Attack Surface Findings
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.
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 10 record(s)
The DNS server responds to ANY queries with 10 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 internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
5 subdomain(s) discovered for ifeng.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 ifeng.com and its subdomains. Each certificate reveals subdomain names.
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.ifeng.com is active and requires authentication.
Reputation Findings
Listed on dnsbl.spfbl.net
139.219.146.10 (ifeng-com.mail.protection.partner.outlook.cn) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.5).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
139.219.17.10 (ifeng-com.mail.protection.partner.outlook.cn) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.5).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Missing Strict-Transport-Security on ifeng.com
The Strict-Transport-Security header is not set on https://ifeng.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://ifeng.com/.well-known/security.txt.
TLS certificate valid for 303 days
Certificate for ifeng.com expires on 2027-03-29.
Certificate issued by TrustAsia OV TLS RSA CA 2024
The certificate for ifeng.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for ifeng.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for ifeng.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for ifeng.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on ifeng.com.
Domain valid for 515 days
Domain ifeng.com expires on 2027-10-26.
Domain transfer and delete locks enabled
Domain ifeng.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for ifeng.com do not match known disposable email provider patterns.
Domain is 7884 days old
Domain ifeng.com was registered 2004-10-26.
No wildcard MX records
No wildcard MX records detected for ifeng.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 (ifeng-com.mail.protection.partner.outlook.cn) uses TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (bjschn02ft007.mail.protection.partner.outlook.cn) aligns with the MX hostname (ifeng-com.mail.protection.partner.outlook.cn).
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.ifeng.com
HTTPS request to https://webmail.ifeng.com failed or timed out.
WHOIS registration data
Registrar: Xin Net Technology Corporation | Created: 2004-10-26 | Expires: 2027-10-26 | Updated: 2024-08-28
WHOIS privacy protection enabled
Domain ifeng.com has WHOIS privacy/redaction enabled.
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: ifng.com (has MX!), ifen.com (has MX!), kfeng.com (has MX!), ideng.com (has MX!), ireng.com (has MX!)
24 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 24. 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: reject
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: reject
⚠️ 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: ifeng-com.mail.protection.partner.outlook.cn
PTR record proves mail server legitimacy
MX: ifeng-com.mail.protection.partner.outlook.cn
Mail server at 139.219.146.10
→
PTR Record
Reverse DNS: mail-sh0chn020010.inbound.protection.outlook.com
Mail Server Reputation: ifeng-com.mail.protection.partner.outlook.cn
RBL check ensures server is not blacklisted
MX: ifeng-com.mail.protection.partner.outlook.cn
Mail server at 139.219.146.10
→
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 policy: reject
→
BIMI Record
BIMI not configured
⚠️ BIMI record is missing. Even with DMARC enforcement, you need to configure BIMI to display your brand logo in supported email clients.
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/ifeng.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan ifeng.com Again