Identity
45
F
xvideos-cdn.com
Posture Score: 44/100
Scanned May 29, 2026 at 3:07 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.xvideos-cdn.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@xvideos-cdn.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); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
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.xvideos-cdn.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.xvideos-cdn.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@xvideos-cdn.com").
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
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.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
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.
Shared/free email hosting detected: alt2.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
Shared/free email hosting detected: alt1.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
Shared/free email hosting detected: aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
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 aspmx5.googlemail.com
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
MX IPs span 5 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2026030601, Refresh: 28800s, Retry: 3600s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Non-routable IPv4 in public DNS: 127.0.0.1
The A record for xvideos-cdn.com contains the non-routable IP address 127.0.0.1. This leaks internal network topology to the public internet.
💡 Implement split-horizon DNS so internal addresses are only served to internal clients. Remove non-routable IPs from public DNS.
Non-routable IPv4 in public DNS: www.xvideos-cdn.com → 127.0.0.1
The subdomain www.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: mail.xvideos-cdn.com → 127.0.0.1
The subdomain mail.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ftp.xvideos-cdn.com → 127.0.0.1
The subdomain ftp.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: smtp.xvideos-cdn.com → 127.0.0.1
The subdomain smtp.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: pop.xvideos-cdn.com → 127.0.0.1
The subdomain pop.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: imap.xvideos-cdn.com → 127.0.0.1
The subdomain imap.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: webmail.xvideos-cdn.com → 127.0.0.1
The subdomain webmail.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: mx.xvideos-cdn.com → 127.0.0.1
The subdomain mx.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ns1.xvideos-cdn.com → 127.0.0.1
The subdomain ns1.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ns2.xvideos-cdn.com → 127.0.0.1
The subdomain ns2.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: vpn.xvideos-cdn.com → 127.0.0.1
The subdomain vpn.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: remote.xvideos-cdn.com → 127.0.0.1
The subdomain remote.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: admin.xvideos-cdn.com → 127.0.0.1
The subdomain admin.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: portal.xvideos-cdn.com → 127.0.0.1
The subdomain portal.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: dev.xvideos-cdn.com → 127.0.0.1
The subdomain dev.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: staging.xvideos-cdn.com → 127.0.0.1
The subdomain staging.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: test.xvideos-cdn.com → 127.0.0.1
The subdomain test.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: api.xvideos-cdn.com → 127.0.0.1
The subdomain api.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: app.xvideos-cdn.com → 127.0.0.1
The subdomain app.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: cdn.xvideos-cdn.com → 127.0.0.1
The subdomain cdn.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: blog.xvideos-cdn.com → 127.0.0.1
The subdomain blog.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: shop.xvideos-cdn.com → 127.0.0.1
The subdomain shop.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: store.xvideos-cdn.com → 127.0.0.1
The subdomain store.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: support.xvideos-cdn.com → 127.0.0.1
The subdomain support.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: help.xvideos-cdn.com → 127.0.0.1
The subdomain help.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: docs.xvideos-cdn.com → 127.0.0.1
The subdomain docs.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: status.xvideos-cdn.com → 127.0.0.1
The subdomain status.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: git.xvideos-cdn.com → 127.0.0.1
The subdomain git.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ci.xvideos-cdn.com → 127.0.0.1
The subdomain ci.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: jenkins.xvideos-cdn.com → 127.0.0.1
The subdomain jenkins.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: grafana.xvideos-cdn.com → 127.0.0.1
The subdomain grafana.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: prometheus.xvideos-cdn.com → 127.0.0.1
The subdomain prometheus.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: kibana.xvideos-cdn.com → 127.0.0.1
The subdomain kibana.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: elastic.xvideos-cdn.com → 127.0.0.1
The subdomain elastic.xvideos-cdn.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
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 13 record(s)
The DNS server responds to ANY queries with 13 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.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
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.
0 subdomain(s) discovered for xvideos-cdn.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 xvideos-cdn.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.xvideos-cdn.com, resolving to 127.0.0.1. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.xvideos-cdn.com responded with HTTP 404.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain xvideos-cdn.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Wildcard MX records detected
Domain xvideos-cdn.com has wildcard MX records, which can be abused for spam or phishing.
💡 Remove wildcard MX records and configure explicit MX entries only for legitimate mail-handling subdomains.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on xvideos-cdn.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
HSTS enabled with preload on webmail.xvideos-cdn.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://xvideos-cdn.com/.well-known/security.txt.
TLS certificate valid for 44 days
Certificate for xvideos-cdn.com expires on 2026-07-13.
Certificate issued by E8
The certificate for xvideos-cdn.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for xvideos-cdn.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for xvideos-cdn.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for xvideos-cdn.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on xvideos-cdn.com.
Domain valid for 88 days
Domain xvideos-cdn.com expires on 2026-08-25.
No disposable email provider MX records
MX records for xvideos-cdn.com do not match known disposable email provider patterns.
Domain is 3198 days old
Domain xvideos-cdn.com was registered 2017-08-25.
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 (aspmx.l.google.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (aspmx.l.google.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
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.
WHOIS registration data
Registrar: NameCheap, Inc. | Created: 2017-08-25 | Expires: 2026-08-25 | Updated: 2026-02-06
WHOIS privacy protection enabled
Domain xvideos-cdn.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: videos-cdn.com (has MX!), xvideos-cn.com
2 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 configured
→
DMARC Policy
DMARC policy missing
⚠️ DMARC policy is missing. Even with DKIM configured, you lack the policy layer that tells receiving servers what to do with authentication failures.
Mail Server Identity: aspmx5.googlemail.com
PTR record proves mail server legitimacy
MX: aspmx5.googlemail.com
Mail server at 142.251.127.27
→
PTR Record
Reverse DNS: lcfrai-in-f27.1e100.net
Mail Server Identity: alt2.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt2.aspmx.l.google.com
Mail server at 142.250.102.27
→
PTR Record
Reverse DNS: rb-in-f27.1e100.net
Mail Server Identity: aspmx3.googlemail.com
PTR record proves mail server legitimacy
MX: aspmx3.googlemail.com
Mail server at 142.250.102.27
→
PTR Record
Reverse DNS: rb-in-f27.1e100.net
Mail Server Identity: alt1.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt1.aspmx.l.google.com
Mail server at 173.194.76.27
→
PTR Record
Reverse DNS: ws-in-f27.1e100.net
Mail Server Identity: aspmx4.googlemail.com
PTR record proves mail server legitimacy
MX: aspmx4.googlemail.com
Mail server at 192.178.213.27
→
PTR Record
Reverse DNS: yugrqzs-in-f27.1e100.net
Mail Server Identity: aspmx.l.google.com
PTR record proves mail server legitimacy
MX: aspmx.l.google.com
Mail server at 209.85.203.27
→
PTR Record
Reverse DNS: dh-in-f27.1e100.net
Mail Server Identity: aspmx2.googlemail.com
PTR record proves mail server legitimacy
MX: aspmx2.googlemail.com
Mail server at 173.194.76.26
→
PTR Record
Reverse DNS: ws-in-f26.1e100.net
Mail Server Reputation: aspmx5.googlemail.com
RBL check ensures server is not blacklisted
MX: aspmx5.googlemail.com
Mail server at 142.251.127.27
→
RBL Status
Not blacklisted
Mail Server Reputation: alt2.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt2.aspmx.l.google.com
Mail server at 142.250.102.27
→
RBL Status
Not blacklisted
Mail Server Reputation: aspmx3.googlemail.com
RBL check ensures server is not blacklisted
MX: aspmx3.googlemail.com
Mail server at 142.250.102.27
→
RBL Status
Not blacklisted
Mail Server Reputation: alt1.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt1.aspmx.l.google.com
Mail server at 173.194.76.27
→
RBL Status
Not blacklisted
Mail Server Reputation: aspmx4.googlemail.com
RBL check ensures server is not blacklisted
MX: aspmx4.googlemail.com
Mail server at 192.178.213.27
→
RBL Status
Not blacklisted
Mail Server Reputation: aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: aspmx.l.google.com
Mail server at 209.85.203.27
→
RBL Status
Not blacklisted
Mail Server Reputation: aspmx2.googlemail.com
RBL check ensures server is not blacklisted
MX: aspmx2.googlemail.com
Mail server at 173.194.76.26
→
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 failure reporting configured
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/xvideos-cdn.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan xvideos-cdn.com Again