perplypad.com

PremiumPublic security posture · Completed

Share on X
$PERPLYPerply PadRobinhood ChainPonsMC $15.9k at scan
0xeD9472660B0fad60239eF676F9111eA749731447
✓ Confirmed: @perplyrh posted this contract addressgmgnDexScreener

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

Security grade

C
Configuration score68/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
2
Medium
3
Low
2
Informational
16 of 23 assessed checks passed · 1 not assessed

Website & claims

What the site says, checked against data
Screenshot of perplypad.com at scan time
perplypad.com · captured at scan time
Page title
Conclave Verify
Domain registered
Oct 21, 2026 · 0 days before this scan
Registrar
Wix.com Ltd.
Contract address on site
None shown
Links on site
None found

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://perplypad.com/
Status
200
HTTP redirects to HTTPSPassed
The unencrypted homepage immediately redirects to HTTPS.
Redirect
301 → https://perplypad.com/
HSTS is enabledPassed
Browsers are told to use HTTPS for 365 days.
Strict-Transport-Security
max-age=31536000
Legacy TLS not assessedNot assessed
Our scanning network could not open a raw TLS connection to this host (proxy request failed, cannot connect to the specified address. It looks like you might be trying to connect to a HTTP-based service — consider using fetch instead).
TLS 1.0
unknown
TLS 1.1
unknown

HTTP security headers

2 findings
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
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
Framing is restrictedPassed
Other sites can't embed this page in a frame.
X-Frame-Options
DENY
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
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.perplypad.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
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://perplypad.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

All checks passed
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.
All 2 referenced contracts have verified sourcePassed
Every address found in the page code has verified source on Sourcify.
0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e
Verified on Ethereum
0xeEeEEEeE14D718C2B47D9923Deab1335E144EeEe
Verified on Ethereum

Wallet stack detected

No wallet or chain libraries recognised in the inspected code.

Inspected 1 script (825 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

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

Agent trace

24 steps · every action the agent took
Show the full trace ↓
  1. 0.0s▸Premium assessment of perplypad.com · budget 100 requests
  2. 0.1s✓Resolved perplypad.com → 216.24.57.1, all public
  3. 0.2s▸Probing HTTPS, HTTP and legacy TLS
  4. 0.7s✓GET https://perplypad.com/ → 200 in 550ms
  5. 0.7s·GET http://perplypad.com/ → 301 https://perplypad.com/
  6. 0.7s·TLS 1.0 probe not possible from this network
  7. 0.7s·TLS 1.1 probe not possible from this network
  8. 0.7s·Security headers present: strict-transport-security, x-frame-options, x-content-type-options, referrer-policy
  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 1 script; reading index-BMNbTeU1.js
  12. 0.8s·index-BMNbTeU1.js (825 KB)
  13. 0.8s·No wallet or chain libraries recognised
  14. 0.8s▸Found 2 contract addresses in page code; checking Sourcify on 6 chains
  15. 0.8s·security.txt not found (HTTP 404)
  16. 1.7s·DNS: DNSSEC off · CAA none · SPF none · DMARC none
  17. 1.8s✓0x0000…2e1e verified on Ethereum
  18. 1.8s✓0xeEeE…EeEe verified on Ethereum
  19. 1.9s✓Graded C (68/100) · 0 high, 2 medium, 3 low · 13 requests to the target
  20. 6.8s✓Rendered the homepage in a browser and saved a screenshot: "Conclave Verify"
  21. 6.8s·Domain registered 2026-10-21 (0 days ago) via Wix.com Ltd.
  22. 6.9s◆Writing summary with openai/gpt-oss-120b and checking the site's claims
  23. 8.6s◆No checkable claims found on the site
  24. 19.5s!Summary unavailable; the report is complete without it

Scope & limitations

Assessment type
Premium, public, non-invasive
Payment
Complimentary
Target
perplypad.com
Final URL
https://perplypad.com/
Resolved addresses
216.24.57.1
Scanned
Oct 21, 2026, 04:32 UTC
Duration
1.9s
Requests made
13 (budget 100)
Report ID
sb7bstdvf7
  • 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.
  • 1 check could not be completed and was excluded from the score: Legacy TLS.

Own perplypad.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.