springahead.com security report

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

28risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

2Medium

4Low

2Info

Collected 14 hours ago5.0sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs2
Registration
DNS posture4
Email authentication2
Certificate
Security headers1
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.

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://www.emburse.com/products/springahead
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://www.emburse.com/products/springahead
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://www.emburse.com/products/springahead
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.emburse.com/products/springahead
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: springahead.com
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: springahead.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: springahead.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: springahead.com

final https://www.emburse.com/products/springaheadstatus 200time 449msstack cloudflare · Next.js

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=63072000
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
✓security.txt published

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com aspmx.l.google.com aspmx2.googlemail.com+1
!SPFends in ~all
v=spf1 ip4:209.34.85.221 include:_spf.google.com include:mailgun.org include:servers.mcsv.net include:mail.zendesk.com ~all
✓DMARCp=quarantine
v=DMARC1; p=quarantine; sp=none; pct=100
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1221.awsdns-24.org ns-1594.awsdns-07.co.uk ns-498.awsdns-62.com ns-878.awsdns-45.net

✓Registered with Amazon Registrar, Inc.22.8 years old
springahead.com
!Registration expiry90 days
2026-12-06
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1221.awsdns-24.org ns-1594.awsdns-07.co.uk ns-498.awsdns-62.com ns-878.awsdns-45.net

Address	Ports	CVEs	Edge	Network
76.76.21.21 springahead.com +2	80443	0	direct	—

Archived URLs

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

springahead.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames