Digital exposure report
upstream.auto
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-20 07:34 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Limit what scripts your pages are allowed to run
This adds one layer of protection against injected scripts.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://upstream.auto/ | grep -i "Content-Security-Policy"
- 2.
Choose which companies may issue certificates for your domain
This reduces the chance of a certificate being issued by a provider you did not choose.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short CAA upstream.auto
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- upstream.auto
- Website request
- GET https://upstream.auto/ → https://upstream.io/
- Scan time
- 2026-11-20 07:34:33 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 27/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 22/30 | Some browser protections are missing. |
| DNS infrastructure | 10/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumCSP — protection from script injection · Hardening gap+8
- 2.LowCAA — who may issue certificates · Hardening gap+5
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 4 of 10 DNS lookups.
v=spf1 include:mailgun.org include:_spf.google.com ip4:85.222.150.192 ip4:85.222.150.193 ip4:85.222.150.194 ip4:85.222.150.195 ip4:85.222.150.196 ip4:85.222.150.197 ip4:85.222.150.198 ip4:85.222.150.199 ip4:85.222.150.200 ip4:85.222.150.201 ip4:85.222.150.202 ip4:85.222.150.203 ip4:85.222.150.204 ip4:85.222.150.205 ip4:85.222.150.206 include:_spf.salesforce.com include:3855866.spf08.hubspotemail.net ~all
$ dig +short TXT upstream.auto
DMARC — anti-spoofing policy
Passed · Severity: OK · 13/15Forged email in the company's name is sent to the spam folder.
Policy p=quarantine. p=quarantine — consider moving to p=reject.
v=DMARC1; p=quarantine; rua=mailto:dmarc@upstream.auto
$ dig +short TXT _dmarc.upstream.auto
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: google. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt0O5Cq4u4xau8cV8SEMTOkPqhtaL…
$ dig +short TXT google._domainkey.upstream.auto
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
8 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
1 aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 inbound-smtp.us-east-1.amazonaws.com 40 aspmx2.googlemail.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 50 aspmx3.googlemail.com
$ dig +short MX upstream.auto
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://upstream.auto/ returned HTTP 200 (final URL: https://upstream.io/). Client-side certificate validation passed.
HTTP 200 Final URL: https://upstream.io/
$ curl -sIL https://upstream.auto/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://upstream.auto/
HTTP 301 Location: https://upstream.auto/
$ curl -sI http://upstream.auto/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. Latest issuance in CT logs: Google Trust Services, expiring 2027-01-26 (67 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: Google Trust Services Valid from: 2026-10-28 Valid until: 2027-01-26 Names: *.upstream.auto, upstream.auto Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect upstream.auto:443 -servername upstream.auto 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
$ curl -sIL https://upstream.auto/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Failed · Severity: Medium · Hardening gap · 0/8Missing Content-Security-Policy header: this removes one layer of protection against script injection.
No Content-Security-Policy header found.
Content-Security-Policy: (missing)
$ curl -sIL https://upstream.auto/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/* Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'
Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: SAMEORIGIN, SAMEORIGIN
X-Frame-Options: SAMEORIGIN, SAMEORIGIN
$ curl -sIL https://upstream.auto/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://upstream.auto/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: strict-origin-when-cross-origin
Referrer-Policy: strict-origin-when-cross-origin
$ curl -sIL https://upstream.auto/ | grep -i "Referrer-Policy"
Permissions-Policy
Passed · Severity: OK · 2/2The site restricts access to sensitive browser features.
Permissions-Policy: geolocation=self
Permissions-Policy: geolocation=self
$ curl -sIL https://upstream.auto/ | grep -i "Permissions-Policy"
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://upstream.auto/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Passed · Severity: OK · 7/7The domain's records are digitally signed and hard to forge.
An AD (Authenticated Data) flag was returned by a validating resolver.
AD = true
$ dig +dnssec upstream.auto | grep -E "flags:.* ad"
CAA — who may issue certificates
Needs attention · Severity: Low · Hardening gap · 0/5Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.
No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.
(no CAA records found)
$ dig +short CAA upstream.auto
- Identify which certificate authority issued your current certificate (see the certificate check).
- Publish CAA for that authority only, and add iodef to receive alerts.
upstream.auto. CAA 0 issue "letsencrypt.org" upstream.auto. CAA 0 iodef "mailto:security@upstream.auto"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
2 NS servers.
phoenix.ns.cloudflare.com vicky.ns.cloudflare.com
$ dig +short NS upstream.auto
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rulesNo gaps observed
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline1 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | upstream.auto | 104.18.26.46 | 104.18.27.46 |
| AAAA | upstream.auto | 2606:4700::6812:1a2e | 2606:4700::6812:1b2e |
| MX | upstream.auto | 1 aspmx.l.google.com | 10 alt3.aspmx.l.google.com | 10 alt4.aspmx.l.google.com | 10 inbound-smtp.us-east-1.amazonaws.com | 40 aspmx2.googlemail.com | 5 alt1.aspmx.l.google.com | 5 alt2.aspmx.l.google.com | 50 aspmx3.googlemail.com |
| NS | upstream.auto | phoenix.ns.cloudflare.com | vicky.ns.cloudflare.com |
| TXT | upstream.auto | MS=ms23401496 | anthropic-domain-verification-7562ca=6Pz1OdedFwekScBHviFWTPOeF | apple-domain-verification=jUOSWhCPMUEBBq2p | ca3-cc0d096dd77a4771ab98c37b21d3d58c | ca3-ccdf70a8a103466ba9d17815681fa2aa | globalsign-domain-verification=0B44240C5DFDB1F075AA14C2A8E959C0 | google-site-verification=--x9IqZiKbT1n2H0o1baWDZvGGi_SGgv5Ec8BryZjEE | google-site-verification=1Wv9bIx5qqpY3i3egSfLfm_x4biHFw_E2KZ-PHZUGBo | google-site-verification=E6U-ijbQtLQbsSzOnPXf3djXOVvTsJLNLqihzQECG-Q | lemlist-verif=a8f2dc5 | openai-domain-verification=dv-PA2RyLtsZ1MNxXToomR2HxYj | v=spf1 include:mailgun.org include:_spf.google.com ip4:85.222.150.192 ip4:85.222.150.193 ip4:85.222.150.194 ip4:85.222.150.195 ip4:85.222.150.196 ip4:85.222.150.197 ip4:85.222.150.198 ip4:85.222.150.199 ip4:85.222.150.200 ip4:85.222.150.201 ip4:85.222.150.202 ip4:85.222.150.203 ip4:85.222.150.204 ip4:85.222.150.205 ip4:85.222.150.206 include:_spf.salesforce.com include:3855866.spf08.hubspotemail.net ~all |
| TXT | _dmarc.upstream.auto | v=DMARC1; p=quarantine; rua=mailto:dmarc@upstream.auto |
| CAA | upstream.auto | — |
| DS | upstream.auto | — |