www.equityvoid.business

PremiumPublic security posture · Completed

Share on X
$EVOIDEquity VoidRobinhood ChainPonsMC $15.8k at scan
0x3527212926471D19D88ffbaD8CF83505735c496d
✓ Confirmed: the project's website lists this contract addressgmgnDexScreener

This report grades the token's website configuration, not the token contract, liquidity or team.

Security grade

D
Configuration score58/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
3
Medium
3
Low
4
Informational
14 of 24 assessed checks passed
Agent summaryExplains the evidence below. It doesn't create findings or change the grade.

Agent summary

Without a Content‑Security‑Policy, any injected script can run in users' browsers, potentially hijacking wallet connection flows or stealing session data. The site already enforces HTTPS, HSTS, and avoids mixed content and third‑party scripts. The remaining work mainly involves adding missing security headers and strengthening email and DNS authentication.

  1. 01Define a strict CSP (e.g., default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none') and use nonces or hashes for any needed inline scripts.Content Security Policymedium
  2. 02Add X-Frame-Options: DENY and Content-Security-Policy: frame-ancestors 'none' to prevent the site from being framed.Framing protectionmedium
  3. 03Publish a DMARC TXT record (e.g., v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain) and monitor reports before moving to p=reject.DMARC policymedium
  4. 04Include X-Content-Type-Options: nosniff in all HTTP responses.MIME type sniffinglow
  5. 05Enable DNSSEC with your DNS provider and add the corresponding DS record at your registrar.DNSSEClow

openai/gpt-oss-120b · 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://www.equityvoid.business/
Status
200
HTTP redirects to HTTPSPassed
The unencrypted homepage immediately redirects to HTTPS.
Redirect
308 → https://www.equityvoid.business/
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

5 findings
mediumConfirmed

No framing protection

Any website can load this page inside an invisible frame and overlay it with misleading content.

X-Frame-Options
(not set)
CSP frame-ancestors
(not set)
Recommendation · Add Content-Security-Policy: frame-ancestors 'none' (or 'self'), and X-Frame-Options: DENY for older browsers.
Why it matters ↓

Without framing protection, another site can embed this one invisibly and trick users into clicking — for example approving a transaction.

How we check: Checks for X-Frame-Options or a CSP frame-ancestors directive.

https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html
mediumConfirmed

Content Security Policy missing

The browser is not told which script sources to trust, so any injected script will run.

Content-Security-Policy
(not set)
Recommendation · Start with a policy such as default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none', then add only the origins the app needs. Use nonces or hashes instead of 'unsafe-inline'.
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
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
(not set)
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
infoConfirmed

Referrer-Policy not set

Modern browsers default to a safe policy, but older ones may send full URLs to other sites.

Referrer-Policy
(not set)
Recommendation · Add Referrer-Policy: strict-origin-when-cross-origin.
Why it matters ↓

URLs can contain tokens, wallet addresses or referral codes. A strict policy keeps them from leaking to third parties.

How we check: Reads the Referrer-Policy header and flags policies that leak full URLs to other sites.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy
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.equityvoid.business
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

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/
CAA records publishedPassed
Certificate issuance is restricted (inherited from equityvoid.business).
CAA equityvoid.business
0 issue "letsencrypt.org"
CAA equityvoid.business
0 issue "pki.goog"
CAA equityvoid.business
0 issue "sectigo.com"

Frontend & disclosure

1 finding
infoConfirmed

No security.txt

There is no published channel for reporting vulnerabilities.

https://www.equityvoid.business/.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
0x3527212926471d19d88ffbad8cf83505735c496d
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 7 scripts and the homepage HTML against published malicious wallet-package releases.
Wallet stack detected
viem, wagmi
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 7 scripts and the homepage HTML reference a source map.

Wallet stack detected

  • viem
  • wagmi

Inspected 7 scripts (946 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

  • 0x3527…496dno Sourcify match

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

Agent trace

27 steps · every action the agent took
Show the full trace ↓
  1. 0.0s▸Premium assessment of www.equityvoid.business · budget 100 requests
  2. 0.0s✓Resolved www.equityvoid.business → 64.29.17.65 (+1 more), all public
  3. 0.1s▸Probing HTTPS, HTTP and legacy TLS
  4. 0.7s✓GET https://www.equityvoid.business/ → 200 in 570ms
  5. 0.7s·GET http://www.equityvoid.business/ → 308 https://www.equityvoid.business/
  6. 0.7s✓TLS 1.0 handshake refused
  7. 0.7s✓TLS 1.1 handshake refused
  8. 0.7s·Security headers present: strict-transport-security
  9. 0.7s·0 cookies set on the homepage
  10. 0.8s▸Reading DNS, security.txt and the page's JavaScript
  11. 0.8s·Homepage references 7 scripts; reading webpack-b381517e57d5a2bb.js, 4bd1b696-c023c6e3521b1417.js, 255-b1e2483a7e02feee.js, main-app-f9b5d20365cb8be2.js, 88-7dbd58929c79dcec.js, page-d1f761a6cd07228a.js
  12. 0.8s·security.txt not found (HTTP 404)
  13. 0.8s·DNS: DNSSEC off · CAA set · SPF none · DMARC none
  14. 1.1s·Following imports: 1 more chunk found; reading polyfills-42372ed130431b0a.js
  15. 1.2s·webpack-b381517e57d5a2bb.js (4 KB)
  16. 1.2s·4bd1b696-c023c6e3521b1417.js (169 KB)
  17. 1.2s·255-b1e2483a7e02feee.js (170 KB)
  18. 1.2s·main-app-f9b5d20365cb8be2.js (1 KB)
  19. 1.2s·88-7dbd58929c79dcec.js (409 KB): viem, wagmi
  20. 1.2s·page-d1f761a6cd07228a.js (83 KB)
  21. 1.2s·polyfills-42372ed130431b0a.js (110 KB)
  22. 1.2s·Wallet stack: viem, wagmi
  23. 1.2s▸Found 1 contract address in page code; checking Sourcify on 6 chains
  24. 2.1s·0x3527…496d: no Sourcify match
  25. 2.2s✓Graded D (58/100) · 0 high, 3 medium, 3 low · 21 requests to the target
  26. 2.3s◆Writing summary with openai/gpt-oss-120b
  27. 13.9s◆Summary ready · 5 prioritized fixes

Scope & limitations

Assessment type
Premium, public, non-invasive
Payment
Complimentary
Target
www.equityvoid.business
Final URL
https://www.equityvoid.business/
Resolved addresses
64.29.17.65, 216.198.79.1
Scanned
Oct 20, 2026, 18:25 UTC
Duration
2.2s
Requests made
21 (budget 100)
Report ID
8exwzze69p
  • 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 www.equityvoid.business? 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.