touredge.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

4Medium

7Low

2Info

Collected 9 hours ago13.5sfrom cache

Certificate Transparency12
DNS resolution7
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs39
Registration
DNS posture2
Email authentication2
Certificate
Security headers4
Archived URLs
Analysis13

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.

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://www.touredge.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://www.touredge.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://www.touredge.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://www.touredge.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://www.touredge.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://www.touredge.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://www.touredge.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://www.touredge.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://www.touredge.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://www.touredge.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: touredge.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: touredge.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: touredge.com

final https://www.touredge.com/status 200time 1578msstack cloudflare

✓http:// redirects to https://
!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 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:12.37.77.90 include:_spf.google.com include:servers.mcsv.net include:mail.zendesk.com ~all
✓DMARCp=reject
v=DMARC1; p=reject; rua=mailto:dmarc-reports@touredge.com; adkim=r; aspf=r
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns39.worldnic.com ns40.worldnic.com

✓Registered with Network Solutions, LLC29.9 years old
touredge.com
✓Registration expiry421 days
2027-11-02
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns39.worldnic.com ns40.worldnic.com

Address	Ports	Edge	Network
23.227.38.74 www.touredge.com +6	80443205220532082208320862087+5	Cloudflare~	—
23.227.38.65 touredge.com +3	80443205220532082208320862087+5	Cloudflare~	—
18.216.71.25 images.touredge.com +5	808144380008069808080838087+3	direct	—
34.149.87.45 wix.touredge.com +3	80443	direct	—
174.143.122.125 facebookadmin.touredge.com	none known	direct	—

Archived URLs

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

touredge.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames