← Back to Scanner

orca.security

Name: orca.security Email Security Posture Assessment
Creator: RacterMX

Posture Score: 86/100

Scanned May 8, 2026 at 4:20 PM UTC

Identity

Attack Surface

Reputation

Identity Findings

Weak DKIM RSA key (~1296 bits) for selector 'google'

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.

high

Weak DKIM RSA key (~1296 bits) for selector 's2'

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.

high

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"

medium

MTA-STS is in testing mode

The MTA-STS policy is in testing mode and not actively enforcing TLS.

💡 Switch mode to "enforce" once TLS is confirmed working for all MX hosts.

low

Shared IP 173.194.76.26 used by multiple MX servers

The IP 173.194.76.26 is shared across 2 MX hostnames, reducing redundancy.

💡 Use unique IP addresses for each MX server for better redundancy.

low

Very low TTL on MX records: 273s

5 MX records have a TTL of 273s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

Very low TTL on TXT records: 33s

37 TXT records have a TTL of 33s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

Very low TTL on SPF records: 33s

2 SPF records have a TTL of 33s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

Very low TTL on DMARC record: 273s

The DMARC record has a TTL of 273s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

NS TTL mismatch between parent and authoritative zone

The NS record TTL in the parent zone (~7173s) differs significantly from the authoritative zone (~86400s).

💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.

low

SPF record is valid

The SPF record is properly configured with valid syntax and within lookup limits.

pass

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

pass

ARC support likely available

MX server software appears to support ARC headers for authentication preservation.

pass

SMTP security checks passed

No open relay, VRFY/EXPN, or banner disclosure issues detected.

pass

SMTP RFC 5321 compliance checks passed

The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.

pass

IPv6 readiness is good

IPv6 records are present and properly configured.

pass

STARTTLS downgrade resistance is adequate

STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.

pass

NS delegation is properly configured

All nameservers are responsive, consistent, and properly secured.

pass

DNS responses are consistent across all nameservers

All authoritative nameservers return consistent answers with proper AA flags.

pass

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.

informational

DMARC alignment: adkim=r, aspf=r

DKIM alignment is relaxed, SPF alignment is relaxed.

informational

DMARC failure reporting: fo=1

Failure reports generated when any authentication mechanism fails.

informational

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.

informational

Deprecated DMARCbis tags found: pct

The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.

informational

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.

informational

Shared/free email hosting detected: ALT1.ASPMX.L.GOOGLE.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: ALT2.ASPMX.L.GOOGLE.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: ASPMX.L.GOOGLE.com

The MX record points to a known shared or free email hosting provider.

informational

No DANE/TLSA records found

DANE is not configured for any MX server. This is optional but provides strong certificate binding.

informational

No BIMI record found

BIMI is not configured. Your brand logo will not display in supporting email clients.

informational

Open mail ports on aspmx3.googlemail.com

Detected open mail-related ports: 25

informational

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.

informational

MX IP network diversity

MX IPs span 3 different /16 networks, providing good diversity.

informational

SOA record parameters

Serial: 2403561369, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s

informational

Attack Surface Findings

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.

medium

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.

medium

No internal information leakage detected

No non-routable IP addresses or internal references were found in public DNS records.

pass

No excessive DNS information exposure detected

No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.

pass

No email autodiscovery endpoints detected

No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.

pass

4 subdomain(s) discovered for orca.security

Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.

informational

0 certificate(s) found in CT logs

Certificate Transparency logs contain 0 certificate(s) for orca.security and its subdomains. Each certificate reveals subdomain names.

informational

Reputation Findings

Missing domain locks: clientDeleteProhibited

Domain orca.security is missing protective locks: clientDeleteProhibited.

💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.

high

HSTS enabled with preload on orca.security

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

pass

security.txt present

Found security.txt at https://orca.security/.well-known/security.txt.

pass

TLS certificate valid for 102 days

Certificate for orca.security expires on 2026-08-18.

pass

Certificate issued by Sectigo Public Server Authentication CA EV R36

The certificate for orca.security is issued by a third-party CA.

pass

Signature algorithm: rsa-sha256

The certificate for orca.security uses an acceptable signature algorithm.

pass

RSA key: 2048 bits

The certificate for orca.security uses an adequate RSA key of 2048 bits.

pass

SCTs present in certificate

The certificate for orca.security contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on orca.security.

pass

Domain valid for 275 days

Domain orca.security expires on 2027-02-07.

pass

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.

informational

Abuse contact lookup failed

Could not query abuse contact information.

informational

PhishTank — API key required

PhishTank phishing database check requires an API key.

informational

Sender Score — API key required

Sender Score reputation check requires an API key.

informational

Cisco Talos — API key required

Cisco Talos IP reputation check requires an API key.

informational

Could not connect to webmail.orca.security

HTTPS request to https://webmail.orca.security failed or timed out.

informational

WHOIS registration data

Registrar: Gandi SAS | Created: 2019-02-07 | Expires: 2027-02-07 | Updated: 2026-03-04

informational

WHOIS privacy protection not detected

Domain orca.security does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.

informational

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: 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.26 → PTR Record Reverse DNS: ws-in-f26.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.26 → PTR Record Reverse DNS: rb-in-f26.1e100.net

Mail Server Identity: ASPMX.L.GOOGLE.com

PTR record proves mail server legitimacy

MX: ASPMX.L.GOOGLE.com Mail server at 74.125.193.26 → PTR Record Reverse DNS: ig-in-f26.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: aspmx3.googlemail.com