Identity
9
D
cisco.com
Posture Score: 65/100
Scanned May 8, 2026 at 3:44 PM UTC
Attack Surface
88
Reputation
99
Identity Findings
Weak DKIM RSA key (~1296 bits) for selector 'selector1'
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.
No STARTTLS support on alln-mx-01.cisco.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on rcdn-mx-01.cisco.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on aer-mx-01.cisco.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on alln-mx-01.cisco.com
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on rcdn-mx-01.cisco.com
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on aer-mx-01.cisco.com
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
NS delegation mismatch
The registrar-delegated nameservers do not match the zone NS records.
💡 Update either the registrar NS delegation or the zone NS records to match.
Inconsistent DNS responses across nameservers
Authoritative nameservers return different answers for the same query.
💡 Verify zone transfers are working correctly and all nameservers serve the same zone data.
SOA serial mismatch across nameservers
Nameservers report different SOA serial numbers, indicating zone transfer lag or failure.
💡 Check zone transfer configuration and ensure all secondary nameservers are receiving updates.
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.cisco.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 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@cisco.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.
IPv6 MX address not accepting SMTP: 2001:420:4621::ad26:d496
The MX server aer-mx-01.cisco.com has AAAA record 2001:420:4621::ad26:d496 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
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.
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.
Deprecated DMARCbis tags found: pct, ri
The DMARC record contains tags deprecated in DMARCbis: pct, ri. Consider removing these for forward compatibility.
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.
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 alln-mx-01.cisco.com
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
MX IPs span 3 different /16 networks, providing good diversity.
SOA record parameters
Serial: 1216485, Refresh: 7200s, Retry: 1800s, Expire: 864000s, Min TTL: 1800s
Authorized certificate authorities
CAA records restrict certificate issuance to: digicert.com, letsencrypt.org, pki.goog, ssl.com, amazon.com, identrust.com, globalsign.com
Attack Surface Findings
DNS ANY query returns 107 record(s)
The DNS server responds to ANY queries with 107 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 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.
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.
18 subdomain(s) discovered for cisco.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 cisco.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
HSTS enabled but missing preload directive on cisco.com
Strict-Transport-Security: max-age=31536000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://cisco.com/.well-known/security.txt.
TLS certificate valid for 135 days
Certificate for cisco.com expires on 2026-09-21.
Certificate issued by HydrantID Server CA O1
The certificate for cisco.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for cisco.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for cisco.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for cisco.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on cisco.com.
Domain valid for 371 days
Domain cisco.com expires on 2027-05-15.
Domain transfer and delete locks enabled
Domain cisco.com has clientTransferProhibited and clientDeleteProhibited locks.
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.cisco.com
HTTPS request to https://webmail.cisco.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 1987-05-14 | Expires: 2027-05-15 | Updated: 2026-04-13
WHOIS privacy protection not detected
Domain cisco.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
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: alln-mx-01.cisco.com
PTR record proves mail server legitimacy
MX: alln-mx-01.cisco.com
Mail server at 173.37.147.230
→
PTR Record
Reverse DNS: alln-mx-01.cisco.com
Mail Server Identity: rcdn-mx-01.cisco.com
PTR record proves mail server legitimacy
MX: rcdn-mx-01.cisco.com
Mail server at 72.163.7.166
→
PTR Record
Reverse DNS: rcdn-mx-01.cisco.com
Mail Server Identity: aer-mx-01.cisco.com
PTR record proves mail server legitimacy
MX: aer-mx-01.cisco.com
Mail server at 173.38.212.150
→
PTR Record
Reverse DNS: aer-mx-01.cisco.com
Mail Server Reputation: alln-mx-01.cisco.com
RBL check ensures server is not blacklisted
MX: alln-mx-01.cisco.com
Mail server at 173.37.147.230
→
RBL Status
Not blacklisted
Mail Server Reputation: rcdn-mx-01.cisco.com
RBL check ensures server is not blacklisted
MX: rcdn-mx-01.cisco.com
Mail server at 72.163.7.166
→
RBL Status
Not blacklisted
Mail Server Reputation: aer-mx-01.cisco.com
RBL check ensures server is not blacklisted
MX: aer-mx-01.cisco.com
Mail server at 173.38.212.150
→
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 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
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/cisco.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan cisco.com Again