Identity
14
D
cyera.io
Posture Score: 67/100
Scanned May 8, 2026 at 4:27 PM UTC
Attack Surface
88
Reputation
99
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 '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.
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.78 (mxa.global.inbound.cf-emailsecurity.net)
The IP 172.65.64.78 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.
No PTR record for MX IP: 172.65.64.78
The IP 172.65.64.78 (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.cyera.io/.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@cyera.io").
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 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 (~7180s) differs significantly from the authoritative zone (~172800s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
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.
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.
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.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
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.
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
DNS ANY query returns 40 record(s)
The DNS server responds to ANY queries with 40 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.
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.
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.
8 subdomain(s) discovered for cyera.io
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 cyera.io and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
HSTS enabled but missing preload directive on cyera.io
Strict-Transport-Security: max-age=31536000; includeSubDomains
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://cyera.io/.well-known/security.txt.
TLS certificate valid for 130 days
Certificate for cyera.io expires on 2026-09-15.
Certificate issued by Amazon RSA 2048 M01
The certificate for cyera.io is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for cyera.io uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for cyera.io uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for cyera.io contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on cyera.io.
Domain valid for 232 days
Domain cyera.io expires on 2026-12-27.
Domain transfer and delete locks enabled
Domain cyera.io 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.cyera.io
HTTPS request to https://webmail.cyera.io failed or timed out.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 2020-12-27 | Expires: 2026-12-27 | Updated: 2026-02-10
WHOIS privacy protection enabled
Domain cyera.io 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 missing
→
DMARC Policy
DMARC policy: quarantine
⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.
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/cyera.io.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan cyera.io Again