Identity
24
F
mailbox.org
Posture Score: 45/100
Scanned May 9, 2026 at 1:13 AM UTC
Attack Surface
18
Reputation
92
Identity Findings
Open recursion on nameserver: dns3.cloudns.net
The nameserver dns3.cloudns.net allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on dns3.cloudns.net or restrict it to trusted networks only.
Open recursion on nameserver: dns4.cloudns.net
The nameserver dns4.cloudns.net allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on dns4.cloudns.net or restrict it to trusted networks only.
Overly broad CIDR range: 2001:67c:2050::/48
The /48 CIDR block authorizes a very large IP range to send email as this domain.
💡 Narrow the IP range to only the specific servers that send email.
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.mailbox.org
No STARTTLS support on mx-n.mailbox.org:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mx-n.mailbox.org
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
NS delegation mismatch
The registrar-delegated nameservers do not match the zone NS records.
💡 Update either the registrar NS delegation or the zone NS records to match.
IPv6 MX address not accepting SMTP: 2001:67c:2050:104:0:ffff:25:1
The MX server mx-n.mailbox.org has AAAA record 2001:67c:2050:104:0:ffff:25:1 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
Very low TTL on A record: 104s
The A record has a TTL of 104s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on NS records: 115s
5 NS records have a TTL of 115s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 114s
5 TXT records have a TTL of 114s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 114s
The SPF record has a TTL of 114s 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 (~114s) differs significantly from the authoritative zone (~300s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
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.
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.
Deprecated DMARCbis tags found: pct, rf
The DMARC record contains tags deprecated in DMARCbis: pct, rf. 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.
DANE/TLSA configured for mx1.mailbox.org
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for mx2.mailbox.org
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for mx3.mailbox.org
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 mx1.mailbox.org
Detected open mail-related ports: 25
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: 2014140145, Refresh: 40000s, Retry: 7200s, Expire: 604800s, Min TTL: 86400s
Authorized certificate authorities
CAA records restrict certificate issuance to: digicert.com, letsencrypt.org, swisssign.com
Attack Surface Findings
Non-routable IPv4 in public DNS: test.mailbox.org → 192.168.100.87
The subdomain test.mailbox.org resolves to non-routable IP 192.168.100.87, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: grafana.mailbox.org → 10.132.0.60
The subdomain grafana.mailbox.org resolves to non-routable IP 10.132.0.60, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: prometheus.mailbox.org → 10.132.0.60
The subdomain prometheus.mailbox.org resolves to non-routable IP 10.132.0.60, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Microsoft Autodiscover accessible without authentication
The Autodiscover endpoint at https://autodiscover.mailbox.org/autodiscover/autodiscover.xml returns configuration data without requiring authentication. This exposes email server details to unauthenticated users.
💡 Configure the Autodiscover endpoint to require authentication before returning configuration data.
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.
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.
Non-responsive IP for www.mailbox.org: 2001:67c:2050:b100:1:443:0:184
The subdomain www.mailbox.org resolves to 2001:67c:2050:b100:1:443:0:184 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2001:67c:2050:b100:1:443:0:184 is operational or remove the DNS record for www.mailbox.org.
Non-responsive IP for staging.mailbox.org: 80.241.63.85
The subdomain staging.mailbox.org resolves to 80.241.63.85 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 80.241.63.85 is operational or remove the DNS record for staging.mailbox.org.
Non-responsive IP for test.mailbox.org: 192.168.100.87
The subdomain test.mailbox.org resolves to 192.168.100.87 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 192.168.100.87 is operational or remove the DNS record for test.mailbox.org.
Non-responsive IP for status.mailbox.org: 2a01:4f8:1c1c:1ea0:0:443:1:1
The subdomain status.mailbox.org resolves to 2a01:4f8:1c1c:1ea0:0:443:1:1 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a01:4f8:1c1c:1ea0:0:443:1:1 is operational or remove the DNS record for status.mailbox.org.
Non-responsive IP for grafana.mailbox.org: 10.132.0.60
The subdomain grafana.mailbox.org resolves to 10.132.0.60 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 10.132.0.60 is operational or remove the DNS record for grafana.mailbox.org.
Non-responsive IP for prometheus.mailbox.org: 10.132.0.60
The subdomain prometheus.mailbox.org resolves to 10.132.0.60 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 10.132.0.60 is operational or remove the DNS record for prometheus.mailbox.org.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
Mozilla Autoconfig endpoint detected
The Autoconfig endpoint at autoconfig.mailbox.org is publicly accessible and exposes mail server configuration details.
💡 Review the autoconfig XML to ensure it does not expose internal server names or sensitive configuration.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
17 subdomain(s) discovered for mailbox.org
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 mailbox.org and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 100 iteration(s) and salt '627815ACE5FFA2DA'.
1 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
Missing domain locks: clientDeleteProhibited
Domain mailbox.org is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS enabled with preload on mailbox.org
Strict-Transport-Security: max-age=15768000; includeSubDomains; preload
security.txt present
Found security.txt at https://mailbox.org/.well-known/security.txt.
TLS certificate valid for 32 days
Certificate for mailbox.org expires on 2026-06-10.
Certificate issued by Thawte TLS RSA CA G1
The certificate for mailbox.org is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for mailbox.org uses an acceptable signature algorithm.
RSA key: 4096 bits
The certificate for mailbox.org uses an adequate RSA key of 4096 bits.
SCTs present in certificate
The certificate for mailbox.org contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on mailbox.org.
Domain valid for 136 days
Domain mailbox.org expires on 2026-09-22.
TLD has good reputation
The .org 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.
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.mailbox.org
HTTPS request to https://webmail.mailbox.org failed or timed out.
WHOIS registration data
Registrar: CPS-Datensysteme GmbH | Created: 1998-09-23 | Expires: 2026-09-22 | Updated: 2025-09-12
WHOIS privacy protection enabled
Domain mailbox.org 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: 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: mx1.mailbox.org
PTR record proves mail server legitimacy
MX: mx1.mailbox.org
Mail server at 80.241.60.212
→
PTR Record
Reverse DNS: mx1.mailbox.org
Mail Server Identity: mx2.mailbox.org
PTR record proves mail server legitimacy
MX: mx2.mailbox.org
Mail server at 80.241.60.215
→
PTR Record
Reverse DNS: mx2.mailbox.org
Mail Server Identity: mx3.mailbox.org
PTR record proves mail server legitimacy
MX: mx3.mailbox.org
Mail server at 80.241.60.216
→
PTR Record
Reverse DNS: mx3.mailbox.org
Mail Server Identity: mx-n.mailbox.org
PTR record proves mail server legitimacy
MX: mx-n.mailbox.org
Mail server at 91.198.250.17
→
PTR Record
Reverse DNS: mx-n.mailbox.org
Mail Server Reputation: mx1.mailbox.org
RBL check ensures server is not blacklisted
MX: mx1.mailbox.org
Mail server at 80.241.60.212
→
RBL Status
Not blacklisted
Mail Server Reputation: mx2.mailbox.org
RBL check ensures server is not blacklisted
MX: mx2.mailbox.org
Mail server at 80.241.60.215
→
RBL Status
Not blacklisted
Mail Server Reputation: mx3.mailbox.org
RBL check ensures server is not blacklisted
MX: mx3.mailbox.org
Mail server at 80.241.60.216
→
RBL Status
Not blacklisted
Mail Server Reputation: mx-n.mailbox.org
RBL check ensures server is not blacklisted
MX: mx-n.mailbox.org
Mail server at 91.198.250.17
→
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
Mode: enforce
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 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/mailbox.org.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan mailbox.org Again