sentinelhood.com

Public security posture · Completed

Share on X

Security grade

B
Configuration score78/100

Grades reflect only the externally visible controls listed below. A good grade does not prove the application is secure. How grades work

0
High
1
Medium
3
Low
2
Informational
18 of 24 assessed checks passed
Agent summaryExplains the evidence below. It doesn't create findings or change the grade.

Agent summary

Without a DMARC policy, receiving mail servers are not instructed on how to handle emails that spoof the sentinelhood.com domain, which could lead to undetected phishing attempts. The site is already doing well in terms of HTTPS and TLS configuration, as well as refraining from disclosing exact versions and using secure cookie flags. The remaining fixes focus on enhancing email security and contract verification.

  1. 01Publish a DMARC policy to instruct receiving mail servers on handling spoofed emailsDMARC policymedium
  2. 02Remove 'unsafe-inline' from the Content Security Policy to reduce the risk of script injectionContent Security Policylow
  3. 03Publish CAA records to restrict which certificate authorities can issue certificates for the domainCAA recordslow
  4. 04Publish an SPF record to declare which servers are authorized to send mail as the domainSPF recordlow
  5. 05Verify the source of every contract users interact with on Sourcify and the relevant block explorerReferenced contract verificationinfo

meta/llama-3.3-70b-instruct-fp8-fast · Workers AI

Website & claims

What the site says, checked against data
Screenshot of sentinelhood.com at scan time
sentinelhood.com · captured at scan time
Page title
Sentinel: Robinhood Chain reader
Domain registered
Oct 16, 2026 · 4 days before this scan
Registrar
Spaceship, Inc.
Contract address on site
0x2da80b9D1bc1B323693C80C76eb4a321ec08CbD0
Links on site
X: x.com/sentinelhoodGitHub: github.com/aeonfun/aeon/pull/1244

No checkable claims found on the site (supply, tax, liquidity, ownership, audits, partners, team or age).

Claims are quoted verbatim from the page. “Matches” and “Doesn't match” come from on-chain data, the token's metadata or public domain records. Anything we can't check against data is marked “Can't verify”, which is not the same as false.

TLS & transport

All checks passed
HTTPS works with a trusted certificatePassed
The homepage loaded over HTTPS and the certificate was accepted.
Final URL
https://sentinelhood.com/
Status
200
HTTP redirects to HTTPSPassed
The unencrypted homepage immediately redirects to HTTPS.
Redirect
308 → https://sentinelhood.com/
HSTS is enabledPassed
Browsers are told to use HTTPS for 730 days.
Strict-Transport-Security
max-age=63072000
Legacy TLS versions are refusedPassed
The server refused handshakes offering only TLS 1.0 or TLS 1.1.
TLS 1.0
rejected
TLS 1.1
rejected

HTTP security headers

1 finding
lowConfirmed

Content Security Policy is permissive

A policy is enforced, but script-src allows 'unsafe-inline'.

Content-Security-Policy
default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src https://fonts.gstatic.com; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'
Recommendation · Remove 'unsafe-inline' and 'unsafe-eval' from script-src and list specific origins. Nonces or hashes with 'strict-dynamic' keep inline bootstraps working.
Why it matters ↓

CSP limits which scripts can run. For dApps it is the main browser-side defence against an injected script draining connected wallets.

How we check: Reads the Content-Security-Policy header and flags policies that still allow inline or arbitrary-origin scripts.

https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
Framing is restrictedPassed
Other sites can't embed this page in a frame.
X-Frame-Options
DENY
CSP frame-ancestors
'none'
MIME sniffing disabledPassed
Browsers will respect declared content types.
X-Content-Type-Options
nosniff
Referrer-Policy is setPassed
Policy: strict-origin-when-cross-origin.
Referrer-Policy
strict-origin-when-cross-origin
Permissions-Policy is setPassed
Access to powerful browser features is restricted.
Permissions-Policy
camera=(), microphone=(), geolocation=(), payment=(), usb=()
No exact versions disclosedPassed
Server headers don't reveal exact software versions.

Cookie configuration

All checks passed
Secure flag: no cookies setPassed
No cookies were set while loading the homepage, so there is nothing to misconfigure here.
HttpOnly: no session cookies setPassed
No cookies were set while loading the homepage, so there is nothing to misconfigure here.
SameSite: no cookies setPassed
No cookies were set while loading the homepage, so there is nothing to misconfigure here.

DNS & email posture

3 findings
mediumConfirmed

No DMARC policy

Receiving mail servers aren't told what to do with mail that spoofs this domain.

Lookup
_dmarc.sentinelhood.com
Recommendation · Publish _dmarc TXT v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain and move to p=reject once reports look clean.
Why it matters ↓

DMARC tells receiving mail servers to reject mail that fails authentication — the main defence against spoofed announcements from your domain.

How we check: Reads the _dmarc TXT record for the domain or its organizational domain and checks the policy.

https://dmarc.org/overview/
lowConfirmed

No SPF record

The domain doesn't declare which servers may send mail as it.

MX
(none)
Recommendation · If the domain never sends mail, publish v=spf1 -all.
Why it matters ↓

SPF lists who may send mail as the domain. Crypto projects are frequent targets of impersonation emails.

How we check: Reads the domain's TXT records for an SPF policy and checks it is not permissive.

https://datatracker.ietf.org/doc/html/rfc7208
lowConfirmed

No CAA records

Any certificate authority may issue certificates for this domain.

Recommendation · Publish CAA records naming the CAs you use, e.g. 0 issue "letsencrypt.org".
Why it matters ↓

CAA restricts which certificate authorities may issue certificates for the domain, reducing the risk of a mis-issued certificate.

How we check: Looks up CAA records for the domain and its parents.

https://datatracker.ietf.org/doc/html/rfc8659
DNSSEC validatedPassed
The resolver authenticated the answer with DNSSEC.
AD flag
set

Frontend & disclosure

1 finding
infoConfirmed

No security.txt

There is no published channel for reporting vulnerabilities.

https://sentinelhood.com/.well-known/security.txt
HTTP 404
Recommendation · Publish /.well-known/security.txt with Contact and Expires fields (see securitytxt.org).
Why it matters ↓

Gives researchers a clear way to report vulnerabilities privately instead of disclosing them publicly.

How we check: Requests /.well-known/security.txt and checks it contains a Contact field and has not expired.

https://securitytxt.org/
No mixed contentPassed
All resources referenced in the homepage HTML use HTTPS or relative URLs.
No third-party scripts in the HTMLPassed
All script tags in the homepage HTML load from the site's own domain.

Web3 frontend

1 finding
infoPotential · needs review

1 of 1 referenced address without verified source on Sourcify

These addresses appear in the page code but have no verified source on Sourcify for Ethereum, Base, Arbitrum One, OP Mainnet, Polygon, BNB Chain. They may be wallets rather than contracts, live on another chain, or be verified elsewhere, such as Etherscan.

Unverified address
0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e
Recommendation · Verify the source of every contract users interact with on Sourcify and the relevant block explorer.
Why it matters ↓

Users should be able to read the code they're asked to interact with. Unverified addresses aren't necessarily unsafe, so this is informational only.

How we check: Extracts EVM addresses referenced in the page code (up to 6) and checks Sourcify for verified source on Ethereum, Base, Arbitrum, OP Mainnet, Polygon and BNB Chain.

https://docs.sourcify.dev/
No known-malicious releases referencedPassed
Checked 1 script and the homepage HTML against published malicious wallet-package releases.
No wallet code loaded from public CDNsPassed
Wallet and chain libraries are not fetched from public CDNs at runtime.
No source maps referencedPassed
None of the 1 script and the homepage HTML reference a source map.

Wallet stack detected

No wallet or chain libraries recognised in the inspected code.

Inspected 1 script (27 KB) that the homepage loads for every visitor, plus the HTML. Lazy-loaded code beyond these may not be covered.

Contracts referenced in page code

  • 0x7eD5…EC7eno Sourcify match

Verification status from Sourcify. Green chains link to the block explorer.

Agent trace

23 steps · every action the agent took
Show the full trace ↓
  1. 0.0s▸Public assessment of sentinelhood.com · budget 60 requests
  2. 0.1s✓Resolved sentinelhood.com → 76.76.21.21, all public
  3. 0.2s▸Probing HTTPS, HTTP and legacy TLS
  4. 0.3s✓GET https://sentinelhood.com/ → 200 in 145ms
  5. 0.3s·GET http://sentinelhood.com/ → 308 https://sentinelhood.com/
  6. 0.3s✓TLS 1.0 handshake refused
  7. 0.3s✓TLS 1.1 handshake refused
  8. 0.3s·Security headers present: strict-transport-security, content-security-policy, x-frame-options, x-content-type-options, referrer-policy, permissions-policy
  9. 0.3s·0 cookies set on the homepage
  10. 0.4s▸Reading DNS, security.txt and the page's JavaScript
  11. 0.4s·Homepage references 1 script; reading index-CNMCWBAu.js
  12. 0.4s·security.txt not found (HTTP 404)
  13. 0.5s·index-CNMCWBAu.js (27 KB)
  14. 0.5s·No wallet or chain libraries recognised
  15. 0.5s▸Found 1 contract address in page code; checking Sourcify on 6 chains
  16. 0.6s·DNS: DNSSEC on · CAA none · SPF none · DMARC none
  17. 1.0s·0x7eD5…EC7e: no Sourcify match
  18. 1.1s✓Graded B (78/100) · 0 high, 1 medium, 3 low · 13 requests to the target
  19. 6.4s✓Rendered the homepage in a browser and saved a screenshot: "Sentinel: Robinhood Chain reader"
  20. 6.4s·Domain registered 2026-10-16 (4 days ago) via Spaceship, Inc.
  21. 6.5s◆Writing summary with meta/llama-3.3-70b-instruct-fp8-fast and checking the site's claims
  22. 10.8s◆No checkable claims found on the site
  23. 13.6s◆Summary ready · 5 prioritized fixes

Scope & limitations

Assessment type
Public, non-invasive
Target
sentinelhood.com
Final URL
https://sentinelhood.com/
Resolved addresses
76.76.21.21
Scanned
Oct 21, 2026, 04:22 UTC
Duration
1.1s
Requests made
13 (budget 60)
Report ID
vh22r5tgg4
  • This is a public, non-invasive assessment of externally visible configuration. It does not test application logic, authentication, APIs, smart contracts or wallet flows.
  • Only the homepage, up to 8 of the scripts it loads, and a few well-known paths were requested. Other pages, lazy-loaded code and subdomains may be configured differently.
  • A good grade means the checked controls are in place. It does not prove the application is secure.

Own sentinelhood.com? Verified owners will be able to request authorized deeper testing and receive findings privately. To dispute a result or opt out of public assessments, see opt-out & abuse reporting.