Identity
29
D
centerpointenergy.com
Posture Score: 64/100
Scanned May 17, 2026 at 7:10 PM UTC
Attack Surface
87
Reputation
77
Identity Findings
Critically weak DKIM key (~1008 bits) for selector 'cm'
RSA keys shorter than 1024 bits are trivially breakable. RFC 8301 requires minimum 1024 bits.
💡 Immediately generate a 2048-bit RSA key pair.
Weak DKIM RSA key (~1008 bits) for selector 'cm'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1008 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
Nameserver unresponsive: ns2.centerpointenergy.com
The nameserver ns2.centerpointenergy.com is not responding on port 53.
💡 Verify that ns2.centerpointenergy.com is properly configured and accessible.
NS delegation mismatch
The registrar-delegated nameservers do not match the zone NS records.
💡 Update either the registrar NS delegation or the zone NS records to match.
Inconsistent DNS responses across nameservers
Authoritative nameservers return different answers for the same query.
💡 Verify zone transfers are working correctly and all nameservers serve the same zone data.
SPF record is 620 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.
DKIM in testing mode for selector 'cm'
The t=y flag indicates DKIM is in testing mode. Receivers may not enforce DKIM failures.
💡 Remove the t=y flag once DKIM signing is verified in production.
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.centerpointenergy.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.
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"
DMARC percentage is 50% (not fully enforced)
Only 50% of messages are subject to the DMARC policy. The remaining messages are treated as p=none.
💡 Increase pct to 100 once confident in SPF/DKIM alignment.
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@centerpointenergy.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.
Slow DNS response from ns2.centerpointenergy.com: 2604.2ms
The nameserver ns2.centerpointenergy.com responded in 2604.2ms, exceeding the 2000ms threshold.
💡 Investigate network latency or performance issues on ns2.centerpointenergy.com.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
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=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
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.
IPv6 readiness is good
IPv6 records are present and properly configured.
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.
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.
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.
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 mxa-0001aa01.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: 2005095361, Refresh: 7200s, Retry: 3600s, Expire: 1209600s, Min TTL: 86400s
Attack Surface Findings
Internal information in TXT record
A TXT record for centerpointenergy.com contains references to internal resources: dc4.sapsf.com
💡 Remove internal hostnames and IP addresses from public TXT records.
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.
DNS ANY query returns 1 record(s)
The DNS server responds to ANY queries with 1 record(s). The low record count limits amplification risk, but ANY responses still aid reconnaissance.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
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 email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
9 subdomain(s) discovered for centerpointenergy.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 centerpointenergy.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Could not retrieve TLS certificate
Failed to connect to centerpointenergy.com:443 or retrieve the peer certificate.
💡 Ensure the domain has a valid TLS certificate installed and port 443 is accessible.
DMARC reports sent to URL shortener domain
DMARC aggregate or forensic reports contain sensitive authentication metadata. Sending them to URL shortener domains indicates misconfiguration or a compromised record.
💡 Change DMARC rua/ruf addresses to a domain you control.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
No disposable email provider MX records
MX records for centerpointenergy.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for centerpointenergy.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mxb-0001aa01.gslb.pphosted.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (mxa-0001aa01.gslb.pphosted.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
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 centerpointenergy.com
HTTPS request to https://centerpointenergy.com failed or timed out.
Could not connect to webmail.centerpointenergy.com
HTTPS request to https://webmail.centerpointenergy.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for centerpointenergy.com.
Could not determine domain age
WHOIS creation date could not be parsed for centerpointenergy.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).
Typosquat detected: ceterpointenergy.com (has MX!), centrpointenergy.com (has MX!), centerointenergy.com (has MX!), centerpintenergy.com (has MX!), centerpoitenergy.com (has MX!)
17 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 17. 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 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-0001aa01.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxa-0001aa01.gslb.pphosted.com
Mail server at 148.163.159.52
→
PTR Record
Reverse DNS: mx0b-0001aa01.pphosted.com
Mail Server Identity: mxb-0001aa01.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxb-0001aa01.gslb.pphosted.com
Mail server at 148.163.159.52
→
PTR Record
Reverse DNS: mx0b-0001aa01.pphosted.com
Mail Server Reputation: mxa-0001aa01.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxa-0001aa01.gslb.pphosted.com
Mail server at 148.163.159.52
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb-0001aa01.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxb-0001aa01.gslb.pphosted.com
Mail server at 148.163.159.52
→
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/centerpointenergy.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan centerpointenergy.com Again