ultrasabers.com security report

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

42risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

4Medium

4Low

2Info

Collected 13 hours ago21.0sfrom cache

Certificate Transparency6
DNS resolution7
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs42
Registration
DNS posture2
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis10

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.
note4 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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://ultrasabers.com/
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://ultrasabers.com/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://ultrasabers.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: ultrasabers.com
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://ultrasabers.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://ultrasabers.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: ultrasabers.com
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: ultrasabers.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: ultrasabers.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: ultrasabers.com

final https://ultrasabers.com/status 200time 18msstack cloudflare · WordPress 7.1

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie __cf_bm
Secure · HttpOnly · SameSite=none

✓Receives mail via 1 server
ultrasabers-com.mail.protection.outlook.com
✓SPFends in -all
v=spf1 a mx include:_spf.ultrasabersemail.com include:spf.protection.outlook.com -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)
✓2 nameservers
kelly.ns.cloudflare.com kianchau.ns.cloudflare.com

✓Registered with IONOS SE20.9 years old
ultrasabers.com
!Registration expiry45 days
2026-10-22
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
kelly.ns.cloudflare.com kianchau.ns.cloudflare.com

Address	Ports	Edge	Network
162.159.130.73 ultrasabers.com +4	80443205220532082208320862087+5	Cloudflare~	—
162.159.129.73 ultrasabers.com +3	80443205220822083208620878080+2	Cloudflare~	—
104.21.20.205 oldsales.ultrasabers.com +1	80443205320822083208620878080+2	Cloudflare~	—
172.67.194.102 oldsales.ultrasabers.com	80443208220832086208780808443+1	Cloudflare~	—
3.222.238.148 store.ultrasabers.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.

ultrasabers.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames