deadroom.lol

PremiumPublic security posture · Completed

Share on X
$DEADROOMDeadroomRobinhood ChainPonsMC $12.3k at scan
0x4ff4C5bF050031F9E8bC105c5117187022353923
✓ 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

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, attackers can spoof emails from deadroom.lol, potentially tricking users into phishing or malicious links. The site already enforces strong transport security—HTTPS with a trusted certificate, HSTS, CSP, and blocks mixed content and third‑party scripts. Remaining work focuses on tightening email authentication, DNS integrity, adding basic security policies, and confirming the legitimacy of the referenced smart‑contract address.

  1. 01Publish a DMARC TXT record (e.g., "v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain") and later move to p=reject after reviewing reports.DMARC policymedium
  2. 02Add an SPF record; if the domain never sends mail, use "v=spf1 -all".SPF recordlow
  3. 03Create CAA records that list the authorized certificate authorities, such as "0 issue \"letsencrypt.org\"".CAA recordslow
  4. 04Enable DNSSEC with your DNS provider and publish the corresponding DS record at the registrar.DNSSEClow
  5. 05Verify the source code of the referenced contract address on Sourcify or the appropriate block explorer and ensure it is audited before user interaction.Referenced contract verificationinfo

openai/gpt-oss-120b · Workers AI

Website & claims

What the site says, checked against data
Screenshot of deadroom.lol at scan time
deadroom.lol · captured at scan time
Page title
Deadroom: raising dead tokens
Domain registered
Unavailable
Registrar
–
Contract address on site
0x4ff4c5bf050031f9e8bc105c5117187022353923
Links on site
X: x.com/_deadroom
✓ Matches

Contract address shown on the website

The site shows 0x4ff4C5bF050031F9E8bC105c5117187022353923.

✓ Matches

X account linked on the website

The site and the token both point to x.com/_deadroom.

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://deadroom.lol/
Status
200
HTTP redirects to HTTPSPassed
The unencrypted homepage immediately redirects to HTTPS.
Redirect
301 → https://deadroom.lol/
HSTS is enabledPassed
Browsers are told to use HTTPS for 180 days, including subdomains.
Strict-Transport-Security
max-age=15552000; includeSubDomains
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
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' data:; connect-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'
Framing is restrictedPassed
Other sites can't embed this page in a frame.
X-Frame-Options
SAMEORIGIN
CSP frame-ancestors
'none'
MIME sniffing disabledPassed
Browsers will respect declared content types.
X-Content-Type-Options
nosniff
Referrer-Policy is setPassed
Policy: no-referrer.
Referrer-Policy
no-referrer
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

4 findings
mediumConfirmed

No DMARC policy

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

Lookup
_dmarc.deadroom.lol
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
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/

Frontend & disclosure

1 finding
infoConfirmed

No security.txt

There is no published channel for reporting vulnerabilities.

https://deadroom.lol/.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
0x4ff4c5bf050031f9e8bc105c5117187022353923
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 (396 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

  • 0x4ff4…3923no Sourcify match

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

Agent trace

22 steps · every action the agent took
Show the full trace ↓
  1. 0.0s▸Premium assessment of deadroom.lol · budget 100 requests
  2. 0.1s✓Resolved deadroom.lol → 69.46.46.80, all public
  3. 0.2s▸Probing HTTPS, HTTP and legacy TLS
  4. 0.3s✓GET https://deadroom.lol/ → 200 in 163ms
  5. 0.3s·GET http://deadroom.lol/ → 301 https://deadroom.lol/
  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
  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-Bq-qz0xF.js
  12. 0.4s·index-Bq-qz0xF.js (396 KB)
  13. 0.4s·No wallet or chain libraries recognised
  14. 0.4s▸Found 1 contract address in page code; checking Sourcify on 6 chains
  15. 0.5s·security.txt not found (HTTP 404)
  16. 0.8s·DNS: DNSSEC off · CAA none · SPF none · DMARC none
  17. 1.2s·0x4ff4…3923: no Sourcify match
  18. 1.3s✓Graded B (78/100) · 0 high, 1 medium, 3 low · 13 requests to the target
  19. 5.8s✓Rendered the homepage in a browser and saved a screenshot: "Deadroom: raising dead tokens"
  20. 6.0s◆Writing summary with openai/gpt-oss-120b and checking the site's claims
  21. 9.0s◆Checked 2 claims: 2 match, 0 don't match, 0 can't be verified
  22. 11.5s◆Summary ready · 5 prioritized fixes

Scope & limitations

Assessment type
Premium, public, non-invasive
Payment
Complimentary
Target
deadroom.lol
Final URL
https://deadroom.lol/
Resolved addresses
69.46.46.80
Scanned
Oct 21, 2026, 06:55 UTC
Duration
1.3s
Requests made
13 (budget 100)
Report ID
egsqghf8vb
  • 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 deadroom.lol? 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.