Identity
84
B
ridley.tech
Posture Score: 84/100
Scanned July 2, 2026 at 12:58 PM UTC
Attack Surface
83
Reputation
85
Identity Findings
MTA-STS policy file unreachable
The MTA-STS policy file at https://mta-sts.ridley.tech/.well-known/mta-sts.txt could not be fetched.
💡 Host the MTA-STS policy file at the well-known URL over HTTPS.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.ridley.tech
ManageSieve port 4190 open on mail.ridley.tech
Port 4190 (ManageSieve) is publicly accessible. This should typically be restricted.
💡 Restrict port 4190 access to authorized networks via firewall rules.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (14 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.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
Subdomains protected (sp=reject)
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.
REQUIRETLS supported
The primary MX advertises REQUIRETLS, providing the strongest possible TLS enforcement for inbound mail.
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.
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.
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.
DANE/TLSA configured for mail.ridley.tech
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 mail.ridley.tech
Detected open mail-related ports: 25, 465, 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
MX IPs span 2 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2, Refresh: 21600s, Retry: 3600s, Expire: 1209600s, Min TTL: 300s
Authorized certificate authorities
CAA records restrict certificate issuance to: letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/3492358366
Attack Surface Findings
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
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.
1 subdomain(s) discovered for ridley.tech
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 ridley.tech and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 1 iteration(s) and salt 'C6339E50BBD57FA3'.
2 email SRV record(s) found
Email service SRV records expose mail server configuration for automatic client setup.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Could not retrieve TLS certificate
Failed to connect to ridley.tech:443 or retrieve the peer certificate.
💡 Ensure the domain has a valid TLS certificate installed and port 443 is accessible.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
Domain valid for 240 days
Domain ridley.tech expires on 2027-02-27.
Domain transfer and delete locks enabled
Domain ridley.tech has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for ridley.tech do not match known disposable email provider patterns.
Domain is 1221 days old
Domain ridley.tech was registered 2023-02-27.
No wildcard MX records
No wildcard MX records detected for ridley.tech.
TLD has good reputation
The .tech 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.ridley.tech) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mail.ridley.tech) aligns with the MX hostname (mail.ridley.tech).
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 ridley.tech
HTTPS request to https://ridley.tech failed or timed out.
Could not connect to webmail.ridley.tech
HTTPS request to https://webmail.ridley.tech failed or timed out.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 2023-02-27 | Expires: 2027-02-27 | Updated: 2026-04-14
WHOIS privacy protection enabled
Domain ridley.tech 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: riley.tech (has MX!)
1 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: 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: mail.ridley.tech
PTR record proves mail server legitimacy
MX: mail.ridley.tech
Mail server at 195.22.135.38
→
PTR Record
Reverse DNS: mail.ridley.tech
Mail Server Identity: backup.ridley.uk
PTR record proves mail server legitimacy
MX: backup.ridley.uk
Mail server at 109.202.246.109
→
PTR Record
Reverse DNS: backup.ridley.uk
Mail Server Reputation: mail.ridley.tech
RBL check ensures server is not blacklisted
MX: mail.ridley.tech
Mail server at 195.22.135.38
→
RBL Status
Not blacklisted
Mail Server Reputation: backup.ridley.uk
RBL check ensures server is not blacklisted
MX: backup.ridley.uk
Mail server at 109.202.246.109
→
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
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/ridley.tech.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan ridley.tech Again