mysafetysign.com security report

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

38risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

1Medium

3Low

2Info

Collected 8 hours ago2.1sfrom cache

Certificate Transparency4
DNS resolution10
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs26
Registration
DNS posture2
Email authentication2
Certificate
Security headers5
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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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://mysafetysign.com/
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://mysafetysign.com/
13.33.88.85 (images.mysafetysign.com) reports bootstrap 5.3.3. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 13.33.88.85
beta.mysafetysign.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: beta.mysafetysign.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: mysafetysign.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: mysafetysign.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: mysafetysign.com

final https://mysafetysign.com/status 403time 22msstack cloudflare

✗http:// redirects to https://
✗Strict-Transport-Security
✓Content-Security-Policy
default-src 'none'; script-src 'nonce-FxwUPoFMoP4fXf49fffDJL' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'…
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
same-origin
✓Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),micro
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie __cf_bm
Secure · HttpOnly · SameSite=none

✓Receives mail via 1 server
mysafetysign-com.mail.protection.outlook.com
!SPFends in ~all
v=spf1 a mx a:xpressmyself.com mx:xpressmyself.com ip4:160.72.182.230 ip4:108.176.9.187/32 ip4:108.176.9.189/32 ip4:65.51.40.226/32 ip4:40.75.21.114/32 ip4:20.81.142.14/32 ip4:18.209.182.237/32 include:servers.mcsv.net include:spf.mandrillapp.com include:_spf.google.com include:spf.protection.outlook.com ~all
✓DMARCp=reject
v=DMARC1; p=reject; fo=1; ri=3600; rua=mailto:90abb9bf178b49d98aa6207071fd8f70@dmarc-reports.cloudflare.net,mailto:smartsign@rua.agari.com; ruf=mailto:smartsign@ruf.agari.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
cory.ns.cloudflare.com gene.ns.cloudflare.com

✓Registered with GoDaddy.com, LLC25.3 years old
mysafetysign.com
✓Registration expiry1349 days
2030-05-18
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
cory.ns.cloudflare.com gene.ns.cloudflare.com

Address	Ports	Edge	Network
104.19.223.152 mysafetysign.com +2	80443205220822083208620872096+3	Cloudflare~	—
104.16.80.172 mysafetysign.com +2	80443208220832087808084438880	Cloudflare~	—
13.33.88.82 images.mysafetysign.com +2	80443	direct	—
13.33.88.85 images.mysafetysign.com +2	80443	direct	—
13.33.88.5 images.mysafetysign.com +2	80443	direct	—
13.33.88.119 images.mysafetysign.com +1	80	direct	—

Archived URLs

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

mysafetysign.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames