vehiclehistory.us security report

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

44risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

13Medium

12Low

2Info

Collected 14 hours ago21.0sfrom cache

Certificate Transparency3
DNS resolution10
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs39
Registration
DNS posture4
Email authentication2
Certificate
Security headers5
Archived URLs
Analysis27

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.
noteNo registration data: RDAP has no record at this level.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
The record ends in ?all, so a spoofed message is neither passed nor failed and most receivers let it through.
What to do
End the record with -all (or ~all while you validate your senders).
asset: vehiclehistory.us
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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.vehiclehistory.us/
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: vehiclehistory.us
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: vehiclehistory.us
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: vehiclehistory.us

final https://www.vehiclehistory.us/status 200time 2428msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
✗Content-Security-Policy
✓Clickjacking protection
DENY
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
✓Permissions-Policy
camera=(), microphone=(), geolocation=(), payment=(self)
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie __sess_vhu
Secure · HttpOnly · SameSite=lax
✗Cookie sessionId
no Secure · no HttpOnly · no SameSite
✗Cookie initialUrl
no Secure · no HttpOnly · no SameSite
✗Cookie variant
no Secure · no HttpOnly · no SameSite
✗Cookie isHeads
no Secure · no HttpOnly · no SameSite
✗Cookie isHeadsV2
no Secure · no HttpOnly · no SameSite
✗Cookie sessionId
no Secure · no HttpOnly · no SameSite
✗Cookie visitedPage
no Secure · no HttpOnly · no SameSite
✗Cookie countdownVH
no Secure · no HttpOnly · no SameSite
✗Cookie referenceId
no Secure · no HttpOnly · no SameSite
✗Cookie referenceId
no Secure · no HttpOnly · no SameSite
✗Cookie searchDateTime
no Secure · no HttpOnly · no SameSite

✓Receives mail via 2 servers
mx1.emailsrvr.com mx2.emailsrvr.com
!SPFends in ?all
v=spf1 include:sendgrid.net include:emailsrvr.com include:_spf.google.com include:spf.mailjet.com ip4:66.96.128.0/18 ?all
✓DMARCp=quarantine
v=DMARC1; p=quarantine; rua=mailto:re+b6dd9a42d348@inbound.dmarcdigests.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-110.awsdns-13.com ns-1185.awsdns-20.org ns-1922.awsdns-48.co.uk ns-672.awsdns-20.net

Address	Ports	Edge	Network
172.64.154.133 jtm.vehiclehistory.us +2	80443205220532082208320862087+5	Cloudflare~	—
104.18.33.123 jtm.vehiclehistory.us +3	80443205220532082208320862087+5	Cloudflare~	—
18.161.111.121 vehiclehistory.us +3	80443	direct	—
18.161.111.4 vehiclehistory.us +3	80443	direct	—
18.161.111.69 vehiclehistory.us +11	80443	direct	—
18.161.111.49 vehiclehistory.us +3	80443	direct	—
13.224.245.110 www.vehiclehistory.us +15	80443	direct	—
13.224.245.44 www.vehiclehistory.us +1	80	direct	—
13.224.245.30 www.vehiclehistory.us +1	80	direct	—
13.224.245.26 www.vehiclehistory.us +1	80	direct	—

Archived URLs

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

vehiclehistory.us security report

Moderate

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames