Identity
90
A
jerrio.net
Posture Score: 94/100
Scanned May 23, 2026 at 5:01 AM UTC
Attack Surface
95
Reputation
96
Identity Findings
MTA-STS policy file unreachable
The MTA-STS policy file at https://mta-sts.jerrio.net/.well-known/mta-sts.txt could not be fetched.
💡 Host the MTA-STS policy file at the well-known URL over HTTPS.
Void lookup: include:_spf.ractermx.com
The mechanism include:_spf.ractermx.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
Shared IP 82.221.100.161 used by multiple MX servers
The IP 82.221.100.161 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
SPF record length OK (37 bytes)
SPF record is within safe DNS packet size limits.
DKIM records are valid
DKIM records found and validated for selectors: default
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).
MX records are valid
All MX records are properly configured.
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
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.
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.
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.
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.
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 mail2.ractermx.com
Detected open mail-related ports: 25, 110, 143, 587, 993, 995
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
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: 2026052001, Refresh: 10800s, Retry: 3600s, Expire: 604800s, Min TTL: 3600s
Authorized certificate authorities
CAA records restrict certificate issuance to: letsencrypt.org
Attack Surface Findings
No NSEC/NSEC3 records found
Neither NSEC nor NSEC3 records were found. Authenticated denial of existence is not configured.
💡 Configure NSEC3 records for authenticated denial of existence while preventing zone enumeration.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
No subdomain takeover risks detected
All checked subdomains have valid, responsive targets.
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 jerrio.net
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 jerrio.net and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 10 iteration(s) and salt 'ABCD'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Missing Strict-Transport-Security on jerrio.net
The Strict-Transport-Security header is not set on https://jerrio.net.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
security.txt present
Found security.txt at https://jerrio.net/.well-known/security.txt.
TLS certificate valid for 74 days
Certificate for jerrio.net expires on 2026-08-06.
Certificate issued by E7
The certificate for jerrio.net is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for jerrio.net uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for jerrio.net uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for jerrio.net contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on jerrio.net.
Domain valid for 328 days
Domain jerrio.net expires on 2027-04-16.
Domain transfer and delete locks enabled
Domain jerrio.net has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for jerrio.net do not match known disposable email provider patterns.
Domain is 36 days old
Domain jerrio.net was registered 2026-04-16.
No wildcard MX records
No wildcard MX records detected for jerrio.net.
TLD has good reputation
The .net 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 (mail.ractermx.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mail.racter.com) aligns with the MX hostname (mail.ractermx.com).
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.jerrio.net
HTTPS request to https://webmail.jerrio.net failed or timed out.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 2026-04-16 | Expires: 2027-04-16 | Updated: 2026-04-16
WHOIS privacy protection enabled
Domain jerrio.net has WHOIS privacy/redaction enabled.
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: errio.net (has MX!), jerro.net (has MX!), merrio.net (has MX!), kerrio.net
4 registered lookalike domain(s) that could be used for phishing against your brand. 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 configured
→
DMARC Policy
DMARC policy: quarantine
Mail Server Identity: mail2.ractermx.com
PTR record proves mail server legitimacy
MX: mail2.ractermx.com
Mail server at 82.221.100.161
→
PTR Record
Reverse DNS: mail.racter.com
Mail Server Identity: mail.ractermx.com
PTR record proves mail server legitimacy
MX: mail.ractermx.com
Mail server at 82.221.100.161
→
PTR Record
Reverse DNS: mail.racter.com
Mail Server Reputation: mail2.ractermx.com
RBL check ensures server is not blacklisted
MX: mail2.ractermx.com
Mail server at 82.221.100.161
→
RBL Status
Not blacklisted
Mail Server Reputation: mail.ractermx.com
RBL check ensures server is not blacklisted
MX: mail.ractermx.com
Mail server at 82.221.100.161
→
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 failure reporting configured
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/jerrio.net.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan jerrio.net Again