Identity
0
B
epam.com
Posture Score: 84/100
Scanned May 17, 2026 at 7:13 AM UTC
Score History
Attack Surface
80
Reputation
88
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.
NSEC used instead of NSEC3 (zone enumeration possible)
The domain uses NSEC records for authenticated denial of existence. NSEC allows zone walking.
💡 Migrate from NSEC to NSEC3 to prevent zone enumeration.
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.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
8 subdomain(s) discovered for epam.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 epam.com and its subdomains. Each certificate reveals subdomain names.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
SMTP banner mismatch: du2pepf00028d11.mail.protection.outlook.com
The SMTP banner identifies as 'du2pepf00028d11.mail.protection.outlook.com' but the MX hostname is 'epam-com.mail.protection.outlook.com' and PTR resolves to 'mail-db7pr03cu00403.inbound.protection.outlook.com'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (epam-com.mail.protection.outlook.com).
Missing Strict-Transport-Security on epam.com
The Strict-Transport-Security header is not set on https://epam.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://epam.com/.well-known/security.txt.
TLS certificate valid for 83 days
Certificate for epam.com expires on 2026-08-08.
Certificate issued by WE1
The certificate for epam.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for epam.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for epam.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for epam.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on epam.com.
Domain valid for 1248 days
Domain epam.com expires on 2029-10-17.
Domain transfer and delete locks enabled
Domain epam.com has clientTransferProhibited and clientDeleteProhibited locks.
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 (epam-com.mail.protection.outlook.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 contact lookup failed
Could not query abuse contact information.
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.epam.com
HTTPS request to https://webmail.epam.com failed or timed out.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 1996-10-18 | Expires: 2029-10-17 | Updated: 2026-04-01
WHOIS privacy protection enabled
Domain epam.com has WHOIS privacy/redaction enabled.
Typosquat detected: eam.com (has MX!), epm.com (has MX!), peam.com (has MX!), epma.com (has MX!), rpam.com (has MX!)
25 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 25. 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: quarantine
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: quarantine
⚠️ 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: epam-com.mail.protection.outlook.com
PTR record proves mail server legitimacy
MX: epam-com.mail.protection.outlook.com
Mail server at 52.101.73.28
→
PTR Record
Reverse DNS: mail-am7pr05cu00204.inbound.protection.outlook.com
Mail Server Reputation: epam-com.mail.protection.outlook.com
RBL check ensures server is not blacklisted
MX: epam-com.mail.protection.outlook.com
Mail server at 52.101.73.28
→
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: quarantine
→
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/epam.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan epam.com Again