onedoorcloses.com security report

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

49risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

3Medium

2Low

2Info

Collected 6 hours ago5.3sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs4
Registration
DNS posture2
Email authentication2
Certificate
Security headers4
Archived URLs
Analysis8

noteCertificate Transparency did not complete (HTTP 502). Results below are partial.
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.

A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://onedoorcloses.com/
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 50.28.12.203:21
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://onedoorcloses.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: onedoorcloses.com
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://onedoorcloses.com/
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: onedoorcloses.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: onedoorcloses.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: onedoorcloses.com

final https://onedoorcloses.com/status 200time 1319msstack cloudflare

✗http:// redirects to https://
✓Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

!Cookie XSRF-TOKEN
Secure · no HttpOnly · SameSite=lax
✓Cookie onedoorclose_session
Secure · HttpOnly · SameSite=lax

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
!SPFends in ~all
v=spf1 ip4:50.28.12.203 +a +mx ~all
!DMARCp=none
v=DMARC1; p=none;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns1.1doorcloses.com ns2.1doorcloses.com

✓Registered with GoDaddy.com, LLC16.5 years old
onedoorcloses.com
✓Registration expiry194 days
2027-03-20
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
ns1.onedoorcloses.com ns2.onedoorcloses.com

Address	Ports	CVEs	Edge	Network
50.28.12.203 onedoorcloses.com +26	215380443	0	direct	—

Archived URLs

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

onedoorcloses.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames