Identity
42
D
yandex.com
Posture Score: 66/100
Scanned May 27, 2026 at 8:01 PM UTC
Attack Surface
85
Reputation
72
Identity Findings
TLSA records without DNSSEC for mx.yandex.ru
DANE requires DNSSEC. Without it, TLSA records provide no security benefit and can be spoofed.
💡 Enable DNSSEC for the domain before relying on DANE/TLSA.
Weak DKIM RSA key (~1296 bits) for selector 'mail'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
External report destination not authorized: yandex.ru
The rua= URI sends reports to yandex.ru, but no authorization record exists at yandex.com._report._dmarc.yandex.ru. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of yandex.ru to publish a TXT record at yandex.com._report._dmarc.yandex.ru containing 'v=DMARC1'.
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.
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.
External DMARC report destination not authorized: yandex.ru
The rua= URI points to yandex.ru but no authorization record exists at yandex.com._report._dmarc.yandex.ru.
💡 Ask the owner of yandex.ru to publish a TXT record at yandex.com._report._dmarc.yandex.ru with 'v=DMARC1'.
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.yandex.com/.well-known/mta-sts.txt
SOA MNAME does not resolve
The primary nameserver (MNAME) 'ns1.yandex.ru' does not resolve to any IP address.
💡 Ensure the MNAME field points to a resolvable, authoritative nameserver.
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@yandex.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 CAA iodef tag configured
No iodef tag is present in the CAA records. CA policy violation reports will not be sent.
💡 Add an iodef CAA record. Example: 0 iodef "mailto:security@example.com"
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (30 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.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
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.
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.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
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.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARC failure reporting: fo=1
Failure reports generated when any authentication mechanism fails.
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.
DANE/TLSA configured for mx.yandex.ru
TLSA records found and TLS certificate is available for verification.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on mx.yandex.ru
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2023042180, Refresh: 3600s, Retry: 900s, Expire: 2592000s, Min TTL: 900s
Authorized certificate authorities
CAA records restrict certificate issuance to: globalsign.com
Attack Surface Findings
Microsoft Autodiscover accessible without authentication
The Autodiscover endpoint at https://autodiscover.yandex.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.
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 6 record(s)
The DNS server responds to ANY queries with 6 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.
Mozilla Autoconfig endpoint detected
The Autoconfig endpoint at autoconfig.yandex.com is publicly accessible and exposes mail server configuration details.
💡 Review the autoconfig XML to ensure it does not expose internal server names or sensitive configuration.
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 yandex.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 yandex.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.yandex.com, resolving to 213.180.204.242. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
2 email SRV record(s) found
Email service SRV records expose mail server configuration for automatic client setup.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain yandex.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
SMTP banner mismatch: mail-nwsmtp-mxfront-production-main-75.sas.yp-c.yandex.net
The SMTP banner identifies as 'mail-nwsmtp-mxfront-production-main-75.sas.yp-c.yandex.net' but the MX hostname is 'mx.yandex.ru' and PTR resolves to 'mxfront.stable.qloud-b.yandex.net'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (mx.yandex.ru).
Missing Strict-Transport-Security on yandex.com
The Strict-Transport-Security header is not set on https://yandex.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Missing Strict-Transport-Security on webmail.yandex.com
The Strict-Transport-Security header is not set on https://webmail.yandex.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Wildcard MX records detected
Domain yandex.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.
security.txt present
Found security.txt at https://yandex.com/.well-known/security.txt.
TLS certificate valid for 71 days
Certificate for yandex.com expires on 2026-08-06.
Certificate issued by GlobalSign ECC OV SSL CA 2018
The certificate for yandex.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for yandex.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for yandex.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for yandex.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on yandex.com.
Domain valid for 118 days
Domain yandex.com expires on 2026-09-23.
No disposable email provider MX records
MX records for yandex.com do not match known disposable email provider patterns.
Domain is 10107 days old
Domain yandex.com was registered 1998-09-24.
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 (mx.yandex.ru) 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.
WHOIS registration data
Registrar: Regional Network Information Center, JSC dba RU-CENTER | Created: 1998-09-24 | Expires: 2026-09-23 | Updated: 2024-11-01
WHOIS privacy protection enabled
Domain yandex.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: andex.com (has MX!), yndex.com (has MX!), yanex.com (has MX!), yandx.com (has MX!), ayndex.com (has MX!)
28 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 28. 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 configured
→
DMARC Policy
DMARC policy: none
Mail Server Identity: mx.yandex.ru
PTR record proves mail server legitimacy
MX: mx.yandex.ru
Mail server at 77.88.21.249
→
PTR Record
Reverse DNS: mxfront.stable.qloud-b.yandex.net
Mail Server Reputation: mx.yandex.ru
RBL check ensures server is not blacklisted
MX: mx.yandex.ru
Mail server at 77.88.21.249
→
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/yandex.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan yandex.com Again