Identity
6
F
ionicsecurity.com
Posture Score: 59/100
Scanned May 11, 2026 at 4:08 PM UTC
Attack Surface
84
Reputation
88
Identity Findings
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.ionicsecurity.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@ionicsecurity.com").
TLSA records without DNSSEC for route2.mx.cloudflare.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 route1.mx.cloudflare.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 route3.mx.cloudflare.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.
No DKIM records found
No DKIM records were found for any common selector. Email may not be authenticated.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.ionicsecurity.com
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: No DMARC record published (required since Feb 2024)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
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.ionicsecurity.com/.well-known/mta-sts.txt
ManageSieve port 4190 open on route2.mx.cloudflare.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@ionicsecurity.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.
Very low TTL on MX records: 280s
3 MX records have a TTL of 280s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 280s
The SPF record has a TTL of 280s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT record: 280s
The TXT 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 (~7196s) differs significantly from the authoritative zone (~86400s).
💡 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.
SPF record length OK (42 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
MX records are valid
All MX records are properly configured.
3 MX records with 3 unique IPs
Multiple MX records provide mail delivery redundancy.
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.
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 route2.mx.cloudflare.net
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for route1.mx.cloudflare.net
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for route3.mx.cloudflare.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 route2.mx.cloudflare.net
Detected open mail-related ports: 25, 110, 143, 465, 587, 993, 995, 4190
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2401185903, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Non-responsive IP for www.ionicsecurity.com: 2606:4700:3030::ac43:ca17
The subdomain www.ionicsecurity.com resolves to 2606:4700:3030::ac43:ca17 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3030::ac43:ca17 is operational or remove the DNS record for www.ionicsecurity.com.
Non-responsive IP for www.ionicsecurity.com: 2606:4700:3036::6815:4ced
The subdomain www.ionicsecurity.com resolves to 2606:4700:3036::6815:4ced which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:4ced is operational or remove the DNS record for www.ionicsecurity.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.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
1 subdomain(s) discovered for ionicsecurity.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 ionicsecurity.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain ionicsecurity.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Missing Strict-Transport-Security on ionicsecurity.com
The Strict-Transport-Security header is not set on https://ionicsecurity.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://ionicsecurity.com/.well-known/security.txt.
TLS certificate valid for 57 days
Certificate for ionicsecurity.com expires on 2026-07-08.
Certificate issued by WE1
The certificate for ionicsecurity.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for ionicsecurity.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for ionicsecurity.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for ionicsecurity.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on ionicsecurity.com.
Domain valid for 330 days
Domain ionicsecurity.com expires on 2027-04-06.
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 (route2.mx.cloudflare.net) uses with cipher including Forward Secrecy.
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 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.ionicsecurity.com
HTTPS request to https://webmail.ionicsecurity.com failed or timed out.
WHOIS registration data
Registrar: Dynadot Inc | Created: 2013-04-06 | Expires: 2027-04-06 | Updated: 2026-03-25
WHOIS privacy protection enabled
Domain ionicsecurity.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 missing
⚠️ DMARC policy is missing. Even with SPF configured, you lack the policy layer that tells receiving servers what to do with authentication failures.
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 missing
⚠️ 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: route2.mx.cloudflare.net
PTR record proves mail server legitimacy
MX: route2.mx.cloudflare.net
Mail server at 162.159.205.19
→
PTR Record
Reverse DNS: route2.mx.cloudflare.net
Mail Server Identity: route1.mx.cloudflare.net
PTR record proves mail server legitimacy
MX: route1.mx.cloudflare.net
Mail server at 162.159.205.11
→
PTR Record
Reverse DNS: route1.mx.cloudflare.net
Mail Server Identity: route3.mx.cloudflare.net
PTR record proves mail server legitimacy
MX: route3.mx.cloudflare.net
Mail server at 162.159.205.24
→
PTR Record
Reverse DNS: route3.mx.cloudflare.net
Mail Server Reputation: route2.mx.cloudflare.net
RBL check ensures server is not blacklisted
MX: route2.mx.cloudflare.net
Mail server at 162.159.205.19
→
RBL Status
Not blacklisted
Mail Server Reputation: route1.mx.cloudflare.net
RBL check ensures server is not blacklisted
MX: route1.mx.cloudflare.net
Mail server at 162.159.205.11
→
RBL Status
Not blacklisted
Mail Server Reputation: route3.mx.cloudflare.net
RBL check ensures server is not blacklisted
MX: route3.mx.cloudflare.net
Mail server at 162.159.205.24
→
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 not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
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/ionicsecurity.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan ionicsecurity.com Again