toneitup.com security report

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

36risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

4Medium

16Low

2Info

Collected 14 hours ago20.8sfrom cache

Domain—

unavailable

Certificate Transparency22
DNS resolution31
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs40
Registration
DNS posture2
Email authentication2
Certificate
Security headers4
Archived URLs
Analysis22

noteFound 22 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 23 addresses; enriching the first 12.
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.
noteRegistration did not complete (Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits). Results below are partial.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://my.toneitup.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://my.toneitup.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://my.toneitup.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://my.toneitup.com/
lr-dev.toneitup.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: lr-dev.toneitup.com
lr-stg.toneitup.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: lr-stg.toneitup.com
staging.toneitup.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: staging.toneitup.com
auth-dev.toneitup.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: auth-dev.toneitup.com
shop-beta.toneitup.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: shop-beta.toneitup.com
dev-subhub.toneitup.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: dev-subhub.toneitup.com
api-staging.toneitup.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: api-staging.toneitup.com
staging-subhub.toneitup.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: staging-subhub.toneitup.com
demo.toneitup.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: demo.toneitup.com
Browsers and the preload list expect at least six months; shorter values give little protection between visits.
What to do
Raise max-age to 31536000 (one year).
asset: https://my.toneitup.com/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://my.toneitup.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://my.toneitup.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://my.toneitup.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://my.toneitup.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://my.toneitup.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: toneitup.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: toneitup.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: toneitup.com

final https://my.toneitup.com/status 200time 839msstack cloudflare

–http:// redirects to https://port 80 did not answer
!Strict-Transport-Security
max-age=7889238
✓Content-Security-Policy
block-all-mixed-content; frame-ancestors 'none'; upgrade-insecure-requests;
✓Clickjacking protection
DENY
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie _shopify_y
no Secure · no HttpOnly · SameSite=lax
✗Cookie _shopify_s
no Secure · no HttpOnly · SameSite=lax
✗Cookie localization
no Secure · no HttpOnly · SameSite=lax
✗Cookie cart_currency
no Secure · no HttpOnly · SameSite=lax
✓Cookie _shopify_essential
Secure · HttpOnly · SameSite=lax
✓Cookie _shopify_analytics
Secure · HttpOnly · SameSite=lax
✓Cookie _shopify_marketing
Secure · HttpOnly · SameSite=lax

✓Receives mail via 7 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com aspmx.l.google.com aspmx2.googlemail.com+3
!SPFends in ~all
v=spf1 include:mailgun.org include:_spf.google.com include:send.toneitup.com ~all
✓DMARCp=quarantine
v=DMARC1; p=quarantine;
!MTA-STSinbound mail can be downgraded to plaintext

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

Address	Ports	Edge	Network
104.21.16.74 toneitup.com +4	80443205220532082208320862087+5	Cloudflare~	—
172.67.166.231 toneitup.com +4	80443205220532082208320862087+5	Cloudflare~	—
44.224.68.31 lr-dev.toneitup.com +2	80443	direct	—
18.162.234.233 auth-dev.toneitup.com +3	80443	direct	—
32.187.24.222 lr.toneitup.com +2	80443	direct	—
63.34.141.205 cms.toneitup.com +2	80443	direct	—
52.35.70.36 lr-dev.toneitup.com +2	443	direct	—
32.188.51.0 lr.toneitup.com +3	443	direct	—
13.224.245.56 staging-subhub.toneitup.com +1	80	direct	—
13.224.245.52 staging-subhub.toneitup.com +1	80	direct	—
13.224.245.40 staging-subhub.toneitup.com +1	80	direct	—
13.224.245.95 staging-subhub.toneitup.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.

toneitup.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames