Identity
60
B
beyondtrust.com
Posture Score: 81/100
Scanned May 8, 2026 at 4:17 PM UTC
Attack Surface
88
Reputation
96
Identity Findings
Open recursion on nameserver: ns-629.awsdns-14.net
The nameserver ns-629.awsdns-14.net allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns-629.awsdns-14.net or restrict it to trusted networks only.
Weak DKIM RSA key (~1296 bits) for selector 'selector2'
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.
Weak DKIM RSA key (~1296 bits) for selector 'mandrill'
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.
Void lookup: include:%{ir}.%{v}.%{d}.spf.has.pphosted.com
The mechanism include:%{ir}.%{v}.%{d}.spf.has.pphosted.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
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.
Shared IP 148.163.142.143 used by multiple MX servers
The IP 148.163.142.143 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Slow DNS response from ns-173.awsdns-21.com: 2076.8ms
The nameserver ns-173.awsdns-21.com responded in 2076.8ms, exceeding the 500ms threshold.
💡 Investigate network latency or performance issues on ns-173.awsdns-21.com.
Very low TTL on A records: 60s
2 A records have a TTL of 60s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 243s
24 TXT records have a TTL of 243s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 243s
The SPF record has a TTL of 243s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 280s
The DMARC record has a TTL of 280s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
NS TTL mismatch between parent and authoritative zone
The NS record TTL in the parent zone (~7186s) differs significantly from the authoritative zone (~172800s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
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.
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
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.
IPv6 readiness is good
IPv6 records are present and properly configured.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
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.
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.
Open mail ports on mxa-00311301.gslb.pphosted.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
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s
Authorized certificate authorities
CAA records restrict certificate issuance to: amazon.com, comodoca.com, digicert.com, globalsign.com, godaddy.com, letsencrypt.org, pki.goog, sectigo.com
Attack Surface Findings
DNS ANY query returns 46 record(s)
The DNS server responds to ANY queries with 46 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.
No NSEC/NSEC3 records found
Neither NSEC nor NSEC3 records were found. Authenticated denial of existence is not configured.
💡 Configure NSEC3 records for authenticated denial of existence while preventing zone enumeration.
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.
5 subdomain(s) discovered for beyondtrust.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 beyondtrust.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
Missing Strict-Transport-Security on beyondtrust.com
The Strict-Transport-Security header is not set on https://beyondtrust.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://beyondtrust.com/.well-known/security.txt.
TLS certificate valid for 65 days
Certificate for beyondtrust.com expires on 2026-07-13.
Certificate issued by WE1
The certificate for beyondtrust.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for beyondtrust.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for beyondtrust.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for beyondtrust.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on beyondtrust.com.
Domain valid for 895 days
Domain beyondtrust.com expires on 2028-10-19.
Domain transfer and delete locks enabled
Domain beyondtrust.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.beyondtrust.com
HTTPS request to https://webmail.beyondtrust.com failed or timed out.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 2004-06-18 | Expires: 2028-10-19 | Updated: 2022-09-15
WHOIS privacy protection enabled
Domain beyondtrust.com has WHOIS privacy/redaction enabled.
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: mxa-00311301.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxa-00311301.gslb.pphosted.com
Mail server at 148.163.142.143
→
PTR Record
Reverse DNS: mx0b-00311301.pphosted.com
Mail Server Identity: mxb-00311301.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxb-00311301.gslb.pphosted.com
Mail server at 148.163.142.143
→
PTR Record
Reverse DNS: mx0b-00311301.pphosted.com
Mail Server Reputation: mxa-00311301.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxa-00311301.gslb.pphosted.com
Mail server at 148.163.142.143
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb-00311301.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxb-00311301.gslb.pphosted.com
Mail server at 148.163.142.143
→
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: enforce
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
BIMI Record
Brand logo configured
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/beyondtrust.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan beyondtrust.com Again