Identity
0
F
evergy.com
Posture Score: 54/100
Scanned May 17, 2026 at 9:31 PM UTC
Attack Surface
92
Reputation
69
Identity Findings
Open recursion on nameserver: ns1-04.azure-dns.com
The nameserver ns1-04.azure-dns.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns1-04.azure-dns.com or restrict it to trusted networks only.
Open recursion on nameserver: ns2-04.azure-dns.net
The nameserver ns2-04.azure-dns.net allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns2-04.azure-dns.net or restrict it to trusted networks only.
Open recursion on nameserver: ns3-04.azure-dns.org
The nameserver ns3-04.azure-dns.org allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns3-04.azure-dns.org or restrict it to trusted networks only.
Open recursion on nameserver: ns4-04.azure-dns.info
The nameserver ns4-04.azure-dns.info allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns4-04.azure-dns.info or restrict it to trusted networks only.
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.
Subdomains have no DMARC enforcement
sp=none explicitly allows unauthenticated mail from subdomains.
💡 Add sp=reject (or sp=quarantine) to your DMARC record to protect subdomains.
VMC URL is not accessible
The VMC URL (cert) returned a non-200 response or is unreachable. Receivers cannot validate the brand logo.
💡 Ensure the VMC PEM file is publicly accessible at the URL specified in the BIMI a= tag.
Subdomain policy (sp=none) is weaker than domain policy (p=reject)
The subdomain policy is less restrictive than the organizational domain policy, leaving subdomains more vulnerable.
💡 Set sp=reject or remove sp= to inherit the domain policy.
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.evergy.com/.well-known/mta-sts.txt
BIMI logo may not be SVG Tiny PS
The logo URL returns Content-Type: . BIMI requires SVG Tiny PS format.
💡 Ensure the logo is in SVG Tiny PS format.
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.
SOA expire value too short
The SOA expire value is 86400s (<604,800s / 7 days). Secondary nameservers may stop serving the zone prematurely.
💡 Increase the SOA expire value to at least 604800 seconds (7 days).
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@evergy.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.
Shared IP 148.163.144.162 used by multiple MX servers
The IP 148.163.144.162 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Very low TTL on MX records: 41s
2 MX records have a TTL of 41s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 40s
8 TXT records have a TTL of 40s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 40s
The SPF record has a TTL of 40s 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.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
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 responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
SPF record is 293 bytes (multi-string TXT)
The SPF record exceeds 255 bytes and requires multi-string TXT encoding. Most modern resolvers handle this correctly.
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.
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.
Open mail ports on mxb-0051b301.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: 2021092701, Refresh: 21600s, Retry: 300s, Expire: 86400s, Min TTL: 21600s
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.
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.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
5 subdomain(s) discovered for evergy.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 evergy.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Listed on dnsbl-2.uceprotect.net
148.163.140.170 (mxb-0051b301.gslb.pphosted.com) is listed on blacklist dnsbl-2.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-2.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl-2.uceprotect.net
148.163.144.162 (mxa-0051b301.gslb.pphosted.com) is listed on blacklist dnsbl-2.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-2.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
HSTS enabled but missing preload directive on evergy.com
Strict-Transport-Security: max-age=31536000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://evergy.com/.well-known/security.txt.
TLS certificate valid for 127 days
Certificate for evergy.com expires on 2026-09-21.
Certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1
The certificate for evergy.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for evergy.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for evergy.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for evergy.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on evergy.com.
Domain valid for 493 days
Domain evergy.com expires on 2027-09-23.
Domain transfer and delete locks enabled
Domain evergy.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for evergy.com do not match known disposable email provider patterns.
Domain is 8756 days old
Domain evergy.com was registered 2002-05-27.
No wildcard MX records
No wildcard MX records detected for evergy.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 (mxb-0051b301.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-0051b301.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 webmail.evergy.com
HTTPS request to https://webmail.evergy.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 2002-05-27 | Expires: 2027-09-23 | Updated: 2025-10-13
WHOIS privacy protection not detected
Domain evergy.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
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: vergy.com (has MX!), evegy.com (has MX!), every.com (has MX!), everg.com (has MX!), evregy.com (has MX!)
15 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 15. 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: 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: mxb-0051b301.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxb-0051b301.gslb.pphosted.com
Mail server at 148.163.140.170
→
PTR Record
Reverse DNS: mx0b-0051b301.pphosted.com
Mail Server Identity: mxa-0051b301.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxa-0051b301.gslb.pphosted.com
Mail server at 148.163.144.162
→
PTR Record
Reverse DNS: mx0a-0051b301.pphosted.com
Mail Server Reputation: mxb-0051b301.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxb-0051b301.gslb.pphosted.com
Mail server at 148.163.140.170
→
RBL Status
Not blacklisted
Mail Server Reputation: mxa-0051b301.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxa-0051b301.gslb.pphosted.com
Mail server at 148.163.144.162
→
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: 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-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/evergy.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan evergy.com Again