trueor.fun

PremiumPublic security posture · Completed

Share on X
$truetrueor.funRobinhood ChainPonsMC $11.8k at scan
0xDa33394FF475f70992E56CE084920AEA6F6e4FBB
✓ Confirmed: @trueorfun posted this contract addressgmgnDexScreener

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

Security grade

D
Configuration score48/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
4
Medium
3
Low
3
Informational
14 of 24 assessed checks passed

TLS & transport

1 finding
mediumConfirmed

HSTS header missing

The site does not tell browsers to always use HTTPS.

Strict-Transport-Security
(not set)
Recommendation · Add Strict-Transport-Security: max-age=31536000; includeSubDomains once every subdomain supports HTTPS.
Why it matters ↓

HSTS tells browsers to never load the site over HTTP again, closing the downgrade window that the redirect alone leaves open.

How we check: Reads the Strict-Transport-Security header on the HTTPS response and checks max-age is at least 180 days.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security
HTTPS works with a trusted certificatePassed
The homepage loaded over HTTPS and the certificate was accepted.
Final URL
https://trueor.fun/
Status
200
HTTP redirects to HTTPSPassed
The unencrypted homepage immediately redirects to HTTPS.
Redirect
301 → https://trueor.fun/
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.trueor.fun
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://trueor.fun/.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

All checks passed
No known-malicious releases referencedPassed
Checked 2 scripts and the homepage HTML against published malicious wallet-package releases.
Wallet stack detected
Privy
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 2 scripts and the homepage HTML reference a source map.
No contract addresses referencedPassed
No EVM addresses were found in 2 scripts and the homepage HTML.

Wallet stack detected

  • Privy

Inspected 2 scripts (51 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

No EVM addresses found in the inspected code.

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

Agent trace

19 steps · every action the agent took
Show the full trace ↓
  1. 0.0s▸Premium assessment of trueor.fun · budget 100 requests
  2. 0.0s✓Resolved trueor.fun → 91.99.73.160, all public
  3. 0.1s▸Probing HTTPS, HTTP and legacy TLS
  4. 1.2s✓GET https://trueor.fun/ → 200 in 1130ms
  5. 1.2s·GET http://trueor.fun/ → 301 https://trueor.fun/
  6. 1.2s✓TLS 1.0 handshake refused
  7. 1.2s✓TLS 1.1 handshake refused
  8. 1.2s·Security headers present: none
  9. 1.2s·0 cookies set on the homepage
  10. 1.3s▸Reading DNS, security.txt and the page's JavaScript
  11. 1.3s·Homepage references 2 scripts; reading privy.js, app.js
  12. 1.3s·DNS: DNSSEC off · CAA none · SPF set · DMARC none
  13. 1.6s·security.txt not found (HTTP 200)
  14. 2.3s·privy.js (4 KB): Privy
  15. 2.3s·app.js (47 KB)
  16. 2.3s·Wallet stack: Privy
  17. 2.4s✓Graded D (48/100) · 0 high, 4 medium, 3 low · 14 requests to the target
  18. 2.5s◆Writing summary with openai/gpt-oss-120b
  19. 14.8s!Summary unavailable; the report is complete without it

Scope & limitations

Assessment type
Premium, public, non-invasive
Payment
Complimentary
Target
trueor.fun
Final URL
https://trueor.fun/
Resolved addresses
91.99.73.160
Scanned
Oct 20, 2026, 22:51 UTC
Duration
2.4s
Requests made
14 (budget 100)
Report ID
3nzussunk5
  • 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 trueor.fun? 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.