on-mailbox.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

32risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

3Medium

2Low

2Info

Collected 14 hours ago44.8sfrom cache

Certificate Transparency1
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs11
Registration
DNS posture2
Email authentication2
Certificate
Security headers4
Archived URLs
Analysis7

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://on-mailbox.com/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: on-mailbox.com
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: on-mailbox.com
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 65.109.175.130:25
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: on-mailbox.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: on-mailbox.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: on-mailbox.com

final https://on-mailbox.com/status 200time 570msstack cloudflare

✓http:// redirects to https://
✗Strict-Transport-Security
✓Content-Security-Policy
default-src https: data: 'unsafe-inline' 'unsafe-eval'
✓Clickjacking protection
sameorigin
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 2 servers
mail.on-mailbox.com mail.on-mailbox.com
!SPFends in ~all
v=spf1 ip4:65.109.175.130 ip6:2a01:4f9:c012:81ba::1 a mx ~all
!DMARCp=none
v=DMARC1; p=none; sp=none; aspf=r; rua=mailto:webmaster@on-mailbox.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
donald.ns.cloudflare.com jule.ns.cloudflare.com

✓Registered with Regtime Ltd.2.6 years old
on-mailbox.com
✓Registration expiry147 days
2027-02-01
✗Transfer lock
none
✓2 nameservers at registry
donald.ns.cloudflare.com jule.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
65.109.175.130 on-mailbox.com +4	2580110143443465587993+3	0	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

on-mailbox.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames