Identity
54
F
co.com
Posture Score: 56/100
Scanned May 29, 2026 at 8:01 PM UTC
Score History
Attack Surface
43
Reputation
72
Identity Findings
Weak DKIM RSA key (~1296 bits) for selector 'k1'
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.
Subdomains have no DMARC enforcement
sp=none explicitly allows unauthenticated mail from subdomains.
💡 Add sp=reject (or sp=quarantine) to your DMARC record to protect subdomains.
Subdomain policy (sp=none) is weaker than domain policy (p=quarantine)
The subdomain policy is less restrictive than the organizational domain policy, leaving subdomains more vulnerable.
💡 Set sp=quarantine or remove sp= to inherit the domain policy.
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.co.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.
SOA MNAME is not authoritative
The primary nameserver (MNAME) 'ns0.nic.co.com' does not return authoritative answers.
💡 Update the MNAME field to point to an authoritative nameserver for this zone.
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"
Void lookup: a:codotcom.kayako.com
The mechanism a:codotcom.kayako.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
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@co.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:978:2:7::162:100
The MX server fallbackmx.spamexperts.eu has AAAA record 2001:978:2:7::162:100 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
IPv6 MX address not accepting SMTP: 2001:978:2:6::f:124
The MX server fallbackmx.spamexperts.eu has AAAA record 2001:978:2:6::f:124 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
No PTR record for IPv6 address: 2001:550:2:61::2fc:100
The IPv6 address 2001:550:2:61::2fc:100 for lastmx.spamexperts.net has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
IPv6 MX address not accepting SMTP: 2001:978:2:7::162:100
The MX server lastmx.spamexperts.net has AAAA record 2001:978:2:7::162:100 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
SPF has ip4 mechanisms but no ip6
The SPF record authorizes IPv4 addresses but not IPv6. Your MX servers have AAAA records, so IPv6 mail delivery is possible without SPF authorization.
💡 Add ip6: mechanisms to the SPF record for your IPv6 mail server addresses.
Shared IP 154.59.104.23 used by multiple MX servers
The IP 154.59.104.23 is shared across 3 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 149.13.75.27 used by multiple MX servers
The IP 149.13.75.27 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
SPF record length OK (137 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 external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
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.
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.
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 mx.spamexperts.com
Detected open mail-related ports: 25, 587
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 4 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2014414078, Refresh: 900s, Retry: 1800s, Expire: 6048000s, Min TTL: 3600s
Attack Surface Findings
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
Non-responsive IP for www.co.com: 173.192.76.171
The subdomain www.co.com resolves to 173.192.76.171 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 173.192.76.171 is operational or remove the DNS record for www.co.com.
Non-responsive IP for ns1.co.com: 75.126.186.11
The subdomain ns1.co.com resolves to 75.126.186.11 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 75.126.186.11 is operational or remove the DNS record for ns1.co.com.
Non-responsive IP for ns2.co.com: 50.22.154.123
The subdomain ns2.co.com resolves to 50.22.154.123 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 50.22.154.123 is operational or remove the DNS record for ns2.co.com.
Non-responsive IP for admin.co.com: 2606:4700:3030::ac43:82dc
The subdomain admin.co.com resolves to 2606:4700:3030::ac43:82dc which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3030::ac43:82dc is operational or remove the DNS record for admin.co.com.
Non-responsive IP for admin.co.com: 2606:4700:3033::6815:97f
The subdomain admin.co.com resolves to 2606:4700:3033::6815:97f which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3033::6815:97f is operational or remove the DNS record for admin.co.com.
Non-responsive IP for staging.co.com: 2606:4700:3031::6815:3e1a
The subdomain staging.co.com resolves to 2606:4700:3031::6815:3e1a which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3031::6815:3e1a is operational or remove the DNS record for staging.co.com.
Non-responsive IP for staging.co.com: 2606:4700:3030::ac43:db17
The subdomain staging.co.com resolves to 2606:4700:3030::ac43:db17 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3030::ac43:db17 is operational or remove the DNS record for staging.co.com.
Non-responsive IP for status.co.com: 2606:4700:3033::ac43:cf94
The subdomain status.co.com resolves to 2606:4700:3033::ac43:cf94 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3033::ac43:cf94 is operational or remove the DNS record for status.co.com.
Non-responsive IP for status.co.com: 2606:4700:3035::6815:16e9
The subdomain status.co.com resolves to 2606:4700:3035::6815:16e9 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3035::6815:16e9 is operational or remove the DNS record for status.co.com.
DNS ANY query returns 21 record(s)
The DNS server responds to ANY queries with 21 record(s), creating significant DNS amplification risk.
💡 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.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
14 subdomain(s) discovered for co.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 co.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.co.com, resolving to 169.60.151.233. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 0 iteration(s) and salt '-'.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.co.com responded with HTTP 400.
Mozilla Autoconfig endpoint detected
The Autoconfig endpoint at autoconfig.co.com is publicly accessible.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain co.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
SMTP banner mismatch: mx307.antispamcloud.com
The SMTP banner identifies as 'mx307.antispamcloud.com' but the MX hostname is 'mx.spamexperts.com' and PTR resolves to 'fe2-r3-in.ams14.l.antispamcloud.com'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (mx.spamexperts.com).
Missing Strict-Transport-Security on co.com
The Strict-Transport-Security header is not set on https://co.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.co.com
The Strict-Transport-Security header is not set on https://webmail.co.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 co.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://co.com/.well-known/security.txt.
TLS certificate valid for 81 days
Certificate for co.com expires on 2026-08-19.
Certificate issued by R13
The certificate for co.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for co.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for co.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for co.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on co.com.
Domain valid for 1173 days
Domain co.com expires on 2029-08-15.
No disposable email provider MX records
MX records for co.com do not match known disposable email provider patterns.
Domain is 10513 days old
Domain co.com was registered 1997-08-16.
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.spamexperts.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 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: Moniker Online Services LLC | Created: 1997-08-16 | Expires: 2029-08-15 | Updated: 2025-11-24
WHOIS privacy protection enabled
Domain co.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: oc.com (has MX!), xo.com (has MX!), fo.com (has MX!), vo.com (has MX!), ci.com (has MX!)
20 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 20. 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 configured
→
DMARC Policy
DMARC policy: quarantine
Mail Server Identity: mx.spamexperts.com
PTR record proves mail server legitimacy
MX: mx.spamexperts.com
Mail server at 154.59.104.23
→
PTR Record
Reverse DNS: fe2-r3-in.ams14.l.antispamcloud.com
Mail Server Identity: fallbackmx.spamexperts.eu
PTR record proves mail server legitimacy
MX: fallbackmx.spamexperts.eu
Mail server at 154.59.104.23
→
PTR Record
Reverse DNS: fe2-r3-in.ams14.l.antispamcloud.com
Mail Server Identity: lastmx.spamexperts.net
PTR record proves mail server legitimacy
MX: lastmx.spamexperts.net
Mail server at 149.13.75.27
→
PTR Record
Reverse DNS: fe1-r3-in.fra02.l.antispamcloud.com
Mail Server Reputation: mx.spamexperts.com
RBL check ensures server is not blacklisted
MX: mx.spamexperts.com
Mail server at 154.59.104.23
→
RBL Status
Not blacklisted
Mail Server Reputation: fallbackmx.spamexperts.eu
RBL check ensures server is not blacklisted
MX: fallbackmx.spamexperts.eu
Mail server at 154.59.104.23
→
RBL Status
Not blacklisted
Mail Server Reputation: lastmx.spamexperts.net
RBL check ensures server is not blacklisted
MX: lastmx.spamexperts.net
Mail server at 149.13.75.27
→
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
Mode:
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 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/co.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan co.com Again