hookable.xyz

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
3
Informational
17 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 hookable.xyz domain, which could lead to undetected phishing attempts. The site is already doing well in terms of HTTPS and TLS configuration, with a trusted certificate and redirects in place. To further improve security, focusing on email authentication and content type handling is key.

  1. 01Publish a DMARC policy to instruct receiving mail servers on handling spoofed emails.DMARC policymedium
  2. 02Add X-Content-Type-Options: nosniff to all responses to prevent browsers from guessing content types.MIME type sniffinglow
  3. 03Enable DNSSEC at the DNS provider and publish the DS record at the registrar to cryptographically sign DNS answers.DNSSEClow
  4. 04Publish CAA records naming the used certificate authorities to restrict certificate issuance.CAA recordslow
  5. 05Publish a security.txt file with contact and expires fields to provide a channel for vulnerability reporting.security.txtinfo

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

TLS & transport

All checks passed
HTTPS works with a trusted certificatePassed
The homepage loaded over HTTPS and the certificate was accepted.
Final URL
https://hookable.xyz/
Status
200
HTTP redirects to HTTPSPassed
The unencrypted homepage immediately redirects to HTTPS.
Redirect
308 → https://hookable.xyz/
HSTS is enabledPassed
Browsers are told to use HTTPS for 365 days.
Strict-Transport-Security
max-age=31536000
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

2 findings
lowConfirmed

X-Content-Type-Options missing

Browsers may guess content types, which can turn a harmless-looking file into executable script.

X-Content-Type-Options
nosniff, nosniff
Recommendation · Add X-Content-Type-Options: nosniff to all responses.
Why it matters ↓

Stops browsers from interpreting uploaded or mislabelled files as scripts or stylesheets.

How we check: Checks that X-Content-Type-Options is set to nosniff.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options
infoConfirmed

Permissions-Policy not set

Embedded content may request browser features the site never uses.

Permissions-Policy
(not set)
Recommendation · Add a policy disabling unused features, e.g. Permissions-Policy: camera=(), microphone=(), geolocation=().
Why it matters ↓

Limits what embedded third-party content can access, such as camera, microphone or payment APIs.

How we check: Checks for a Permissions-Policy header restricting powerful browser features.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy
Content Security Policy is enforcedPassed
Script sources are restricted by an enforced policy.
Content-Security-Policy
default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; connect-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'
Framing is restrictedPassed
Other sites can't embed this page in a frame.
X-Frame-Options
DENY, DENY
CSP frame-ancestors
'none'
Referrer-Policy is setPassed
Policy: strict-origin-when-cross-origin.
Referrer-Policy
strict-origin-when-cross-origin, strict-origin-when-cross-origin
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.hookable.xyz
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 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
lowConfirmed

DNSSEC not enabled

DNS answers for this domain are not cryptographically signed.

AD flag
not set
Recommendation · Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
Why it matters ↓

DNSSEC prevents forged DNS answers from sending visitors to a look-alike server.

How we check: Resolves the domain through a validating resolver and checks whether the answer is DNSSEC-authenticated.

https://www.cloudflare.com/dns/dnssec/how-dnssec-works/
SPF record publishedPassed
Authorised mail senders are declared.
TXT
v=spf1 include:spf.efwd.registrar-servers.com ~all

Frontend & disclosure

1 finding
infoConfirmed

No security.txt

There is no published channel for reporting vulnerabilities.

https://hookable.xyz/.well-known/security.txt
HTTP 200
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
0xebfe1c9ac846c5d3bbef0a08fccbc698ded4f516
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 (254 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

  • 0xebfe…f516no Sourcify match

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

Agent trace

20 steps · every action the agent took
Show the full trace ↓
  1. 0.0s▸Public assessment of hookable.xyz · budget 60 requests
  2. 0.0s✓Resolved hookable.xyz → 168.100.11.225, all public
  3. 0.1s▸Probing HTTPS, HTTP and legacy TLS
  4. 1.0s✓GET https://hookable.xyz/ → 200 in 901ms
  5. 1.0s·GET http://hookable.xyz/ → 308 https://hookable.xyz/
  6. 1.0s✓TLS 1.0 handshake refused
  7. 1.0s✓TLS 1.1 handshake refused
  8. 1.0s·Security headers present: strict-transport-security, content-security-policy, x-frame-options, x-content-type-options, referrer-policy
  9. 1.0s·0 cookies set on the homepage
  10. 1.1s▸Reading DNS, security.txt and the page's JavaScript
  11. 1.1s·Homepage references 1 script; reading index-Bos82XYW.js
  12. 1.2s·DNS: DNSSEC off · CAA none · SPF set · DMARC none
  13. 1.3s·security.txt not found (HTTP 200)
  14. 2.0s·index-Bos82XYW.js (254 KB)
  15. 2.0s·No wallet or chain libraries recognised
  16. 2.0s▸Found 1 contract address in page code; checking Sourcify on 6 chains
  17. 2.6s·0xebfe…f516: no Sourcify match
  18. 2.7s✓Graded B (78/100) · 0 high, 1 medium, 3 low · 13 requests to the target
  19. 2.8s◆Writing summary with meta/llama-3.3-70b-instruct-fp8-fast
  20. 20.1s◆Summary ready · 5 prioritized fixes

Scope & limitations

Assessment type
Public, non-invasive
Target
hookable.xyz
Final URL
https://hookable.xyz/
Resolved addresses
168.100.11.225
Scanned
Oct 20, 2026, 17:05 UTC
Duration
2.7s
Requests made
13 (budget 60)
Report ID
d8hfd6uqkx
  • 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 hookable.xyz? 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.