← Back to Scanner

broadcom.com

Name: broadcom.com Email Security Posture Assessment
Creator: RacterMX

Posture Score: 68/100

Scanned May 8, 2026 at 4:05 PM UTC

Identity

Attack Surface

Reputation

100

Identity Findings

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

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 '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

FCrDNS failure: no PTR for 216.239.32.151 (mx1.smtp.goog)

The IP 216.239.32.151 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.

💡 Configure a PTR record for the IP that matches the mail server hostname.

high

FCrDNS failure: no PTR for 216.239.34.151 (mx2.smtp.goog)

The IP 216.239.34.151 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.

💡 Configure a PTR record for the IP that matches the mail server hostname.

high

FCrDNS failure: no PTR for 216.239.36.151 (mx3.smtp.goog)

The IP 216.239.36.151 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.

💡 Configure a PTR record for the IP that matches the mail server hostname.

high

FCrDNS failure: no PTR for 216.239.38.151 (mx4.smtp.goog)

The IP 216.239.38.151 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.

💡 Configure a PTR record for the IP that matches the mail server hostname.

high

No PTR record for MX IP: 216.239.32.151

The IP 216.239.32.151 (for mx1.smtp.goog) has no reverse DNS record.

💡 Configure a PTR record for the mail server IP.

medium

No PTR record for MX IP: 216.239.34.151

The IP 216.239.34.151 (for mx2.smtp.goog) has no reverse DNS record.

💡 Configure a PTR record for the mail server IP.

medium

No PTR record for MX IP: 216.239.36.151

The IP 216.239.36.151 (for mx3.smtp.goog) has no reverse DNS record.

💡 Configure a PTR record for the mail server IP.

medium

No PTR record for MX IP: 216.239.38.151

The IP 216.239.38.151 (for mx4.smtp.goog) has no reverse DNS record.

💡 Configure a PTR record for the mail server IP.

medium

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.broadcom.com/.well-known/mta-sts.txt

medium

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.

medium

SOA MNAME does not resolve

The primary nameserver (MNAME) 'acc-gmc.broadcom.net' does not resolve to any IP address.

💡 Ensure the MNAME field points to a resolvable, authoritative nameserver.

medium

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

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@broadcom.com").

low

No PTR record for IPv6 address: 2001:4860:4802:32::97

The IPv6 address 2001:4860:4802:32::97 for mx1.smtp.goog has no reverse DNS record.

💡 Configure a PTR record for the IPv6 address.

low

No PTR record for IPv6 address: 2001:4860:4802:34::97

The IPv6 address 2001:4860:4802:34::97 for mx2.smtp.goog has no reverse DNS record.

💡 Configure a PTR record for the IPv6 address.

low

No PTR record for IPv6 address: 2001:4860:4802:36::97

The IPv6 address 2001:4860:4802:36::97 for mx3.smtp.goog has no reverse DNS record.

💡 Configure a PTR record for the IPv6 address.

low

No PTR record for IPv6 address: 2001:4860:4802:38::97

The IPv6 address 2001:4860:4802:38::97 for mx4.smtp.goog has no reverse DNS record.

💡 Configure a PTR record for the IPv6 address.

low

Very low TTL on MX records: 274s

7 MX records have a TTL of 274s or less (below 300s).

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

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

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

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: aspmx.l.google.com

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

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

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 mx1.smtp.goog

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 4 different /16 networks, providing good diversity.

informational

SOA record parameters

Serial: 2017710621, Refresh: 600s, Retry: 60s, Expire: 2592000s, Min TTL: 300s

informational

Attack Surface Findings

Domain enumerability: low

The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.

low

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

12 subdomain(s) discovered for broadcom.com

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 broadcom.com and its subdomains. Each certificate reveals subdomain names.

informational

NSEC3 authenticated denial of existence

The domain uses NSEC3 with 10 iteration(s) and salt '6BFBF145456CB924DA1F'.

informational

DNSSEC is enabled

DNSKEY and/or DS records are present, indicating DNSSEC is configured.

informational

Reputation Findings

HSTS enabled with preload on broadcom.com

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

pass

security.txt present

Found security.txt at https://broadcom.com/.well-known/security.txt.

pass

TLS certificate valid for 316 days

Certificate for broadcom.com expires on 2027-03-20.

pass

Certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1

The certificate for broadcom.com is issued by a third-party CA.

pass

Signature algorithm: rsa-sha256

The certificate for broadcom.com uses an acceptable signature algorithm.

pass

RSA key: 2048 bits

The certificate for broadcom.com uses an adequate RSA key of 2048 bits.

pass

SCTs present in certificate

The certificate for broadcom.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on broadcom.com.

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.broadcom.com

HTTPS request to https://webmail.broadcom.com failed or timed out.

informational

WHOIS lookup failed

Could not retrieve WHOIS data for broadcom.com.

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 configured → DMARC Policy DMARC policy: reject

Mail Server Identity: mx1.smtp.goog

PTR record proves mail server legitimacy

MX: mx1.smtp.goog Mail server at 216.239.32.151 → PTR Record No PTR record

⚠️ Mail server mx1.smtp.goog (216.239.32.151) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.

Mail Server Identity: mx2.smtp.goog

PTR record proves mail server legitimacy

MX: mx2.smtp.goog Mail server at 216.239.34.151 → PTR Record No PTR record

⚠️ Mail server mx2.smtp.goog (216.239.34.151) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.

Mail Server Identity: aspmx.l.google.com

PTR record proves mail server legitimacy

MX: aspmx.l.google.com Mail server at 209.85.203.27 → PTR Record Reverse DNS: dh-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.27 → PTR Record Reverse DNS: ws-in-f27.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: mx3.smtp.goog

PTR record proves mail server legitimacy

MX: mx3.smtp.goog Mail server at 216.239.36.151 → PTR Record No PTR record

⚠️ Mail server mx3.smtp.goog (216.239.36.151) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.

Mail Server Identity: mx4.smtp.goog

PTR record proves mail server legitimacy

MX: mx4.smtp.goog Mail server at 216.239.38.151 → PTR Record No PTR record

⚠️ Mail server mx4.smtp.goog (216.239.38.151) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.

Mail Server Reputation: mx1.smtp.goog