Identity
7
F
monolithicpower.com
Posture Score: 54/100
Scanned May 18, 2026 at 1:05 AM UTC
Attack Surface
88
Reputation
66
Identity Findings
TLSA records without DNSSEC for mxa.global.inbound.cf-emailsecurity.net
DANE requires DNSSEC. Without it, TLSA records provide no security benefit and can be spoofed.
💡 Enable DNSSEC for the domain before relying on DANE/TLSA.
TLSA records without DNSSEC for mxb.global.inbound.cf-emailsecurity.net
DANE requires DNSSEC. Without it, TLSA records provide no security benefit and can be spoofed.
💡 Enable DNSSEC for the domain before relying on DANE/TLSA.
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.
Port 465 open but TLS handshake failed on mxa.global.inbound.cf-emailsecurity.net
Port 465 (SMTPS) is open but does not complete a TLS handshake.
💡 Ensure TLS is properly configured on port 465.
FCrDNS failure: no PTR for 172.65.64.137 (mxa.global.inbound.cf-emailsecurity.net)
The IP 172.65.64.137 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.
FCrDNS failure: no PTR for 141.101.90.40 (mxb.global.inbound.cf-emailsecurity.net)
The IP 141.101.90.40 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.
SPF record is 463 bytes (UDP truncation risk)
SPF records exceeding ~450 bytes risk UDP truncation, causing TCP fallback failures on some resolvers. This can lead to intermittent SPF failures.
💡 Consolidate SPF mechanisms, remove unused includes, or use an SPF flattening service to reduce record size.
No PTR record for MX IP: 172.65.64.137
The IP 172.65.64.137 (for mxa.global.inbound.cf-emailsecurity.net) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 141.101.90.40
The IP 141.101.90.40 (for mxb.global.inbound.cf-emailsecurity.net) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
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.monolithicpower.com/.well-known/mta-sts.txt
ManageSieve port 4190 open on mxa.global.inbound.cf-emailsecurity.net
Port 4190 (ManageSieve) is publicly accessible. This should typically be restricted.
💡 Restrict port 4190 access to authorized networks via firewall rules.
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"
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@monolithicpower.com").
Slow DNS response from ns-131.awsdns-16.com: 2073.7ms
The nameserver ns-131.awsdns-16.com responded in 2073.7ms, exceeding the 2000ms threshold.
💡 Investigate network latency or performance issues on ns-131.awsdns-16.com.
Very low TTL on MX records: 50s
2 MX records have a TTL of 50s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on NS records: 282s
4 NS records have a TTL of 282s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 43s
16 TXT records have a TTL of 43s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 43s
The SPF record has a TTL of 43s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 1s
The DMARC record has a TTL of 1s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
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.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
Subdomains protected (sp=quarantine)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
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.
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.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
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.
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.
DANE/TLSA configured for mxa.global.inbound.cf-emailsecurity.net
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for mxb.global.inbound.cf-emailsecurity.net
TLSA records found and TLS certificate is available for verification.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on mxa.global.inbound.cf-emailsecurity.net
Detected open mail-related ports: 25, 110, 143, 465, 587, 993, 995, 4190
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 2 different /16 networks, providing good diversity.
SOA record parameters
Serial: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s
Attack Surface Findings
Non-responsive IP for jenkins.monolithicpower.com: 34.217.219.198
The subdomain jenkins.monolithicpower.com resolves to 34.217.219.198 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 34.217.219.198 is operational or remove the DNS record for jenkins.monolithicpower.com.
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.
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.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
4 subdomain(s) discovered for monolithicpower.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 monolithicpower.com and its subdomains. Each certificate reveals subdomain names.
1 email SRV record(s) found
Email service SRV records expose mail server configuration for automatic client setup.
Reputation Findings
Listed on dnsbl-3.uceprotect.net
172.65.64.78 (mxa.global.inbound.cf-emailsecurity.net) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-3.uceprotect.net
141.101.90.40 (mxb.global.inbound.cf-emailsecurity.net) is listed on blacklist dnsbl-3.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-3.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Missing Strict-Transport-Security on monolithicpower.com
The Strict-Transport-Security header is not set on https://monolithicpower.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://monolithicpower.com/.well-known/security.txt.
TLS certificate valid for 71 days
Certificate for monolithicpower.com expires on 2026-07-28.
Certificate issued by R12
The certificate for monolithicpower.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for monolithicpower.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for monolithicpower.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for monolithicpower.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on monolithicpower.com.
No disposable email provider MX records
MX records for monolithicpower.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for monolithicpower.com.
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 (mxa.global.inbound.cf-emailsecurity.net) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mxa.india.inbound.cf-emailsecurity.net) aligns with the MX hostname (mxa.global.inbound.cf-emailsecurity.net).
No registered typosquat domains detected
None of the common typosquat mutations of this domain appear to be registered by third parties.
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.
Could not connect to webmail.monolithicpower.com
HTTPS request to https://webmail.monolithicpower.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for monolithicpower.com.
Could not determine domain age
WHOIS creation date could not be parsed for monolithicpower.com.
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).
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 missing
→
DMARC Policy
DMARC policy: quarantine
⚠️ 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.global.inbound.cf-emailsecurity.net
PTR record proves mail server legitimacy
MX: mxa.global.inbound.cf-emailsecurity.net
Mail server at 172.65.64.78
→
PTR Record
No PTR record
⚠️ Mail server mxa.global.inbound.cf-emailsecurity.net (172.65.64.78) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mxb.global.inbound.cf-emailsecurity.net
PTR record proves mail server legitimacy
MX: mxb.global.inbound.cf-emailsecurity.net
Mail server at 141.101.90.40
→
PTR Record
No PTR record
⚠️ Mail server mxb.global.inbound.cf-emailsecurity.net (141.101.90.40) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: mxa.global.inbound.cf-emailsecurity.net
RBL check ensures server is not blacklisted
MX: mxa.global.inbound.cf-emailsecurity.net
Mail server at 172.65.64.78
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb.global.inbound.cf-emailsecurity.net
RBL check ensures server is not blacklisted
MX: mxb.global.inbound.cf-emailsecurity.net
Mail server at 141.101.90.40
→
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
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
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-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
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/monolithicpower.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan monolithicpower.com Again