www.coronerai.pro

PremiumPublic security posture · Completed

Share on X

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
1
Informational
17 of 23 assessed checks passed · 1 not assessed
Agent summaryExplains the evidence below. It doesn't create findings or change the grade.

Agent summary

Without an HSTS header browsers can be tricked into loading the site over plain HTTP, exposing visitors to man‑in‑the‑middle interception. The site already enforces HTTPS with a valid certificate, uses a strong Content‑Security‑Policy, and has secure cookie and referrer settings. Remaining work focuses on strengthening transport‑level and email‑related protections and adding DNS hardening records.

  1. 01Configure the web server to send Strict-Transport-Security: max-age=31536000; includeSubDomains once all subdomains support HTTPS.HTTP Strict Transport Securitymedium
  2. 02Publish 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
  3. 03Enable DNSSEC with your DNS provider and publish the corresponding DS record at the registrar.DNSSEClow
  4. 04Create CAA records that authorize only the CAs you use, such as 0 issue "letsencrypt.org".CAA recordslow
  5. 05Add an SPF TXT record; if the domain never sends mail, use v=spf1 -all.SPF recordlow

openai/gpt-oss-120b · Workers AI

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://www.coronerai.pro/
Status
200
HTTP redirects to HTTPSPassed
The unencrypted homepage immediately redirects to HTTPS.
Redirect
301 → https://www.coronerai.pro/
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

All checks passed
Content Security Policy is enforcedPassed
Script sources are restricted by an enforced policy.
Content-Security-Policy
default-src 'self'; script-src 'self' https://challenges.cloudflare.com https://static.cloudflareinsights.com; frame-src https://challenges.cloudflare.com; connect-src 'self' https://cloudflareinsights.com https://robinhoodchain.blockscout.com https://api.geckoterminal.com https://raw.githubusercont…
Framing is restrictedPassed
Other sites can't embed this page in a frame.
X-Frame-Options
DENY
CSP frame-ancestors
'none'
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
Permissions-Policy is setPassed
Access to powerful browser features is restricted.
Permissions-Policy
camera=(), microphone=(), geolocation=(), payment=()
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.coronerai.pro
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://www.coronerai.pro/.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 3 scripts 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 3 scripts and the homepage HTML reference a source map.
No contract addresses referencedPassed
No EVM addresses were found in 3 scripts and the homepage HTML.

Wallet stack detected

No wallet or chain libraries recognised in the inspected code.

Inspected 3 scripts (8 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

20 steps · every action the agent took
Show the full trace ↓
  1. 0.0s▸Premium assessment of www.coronerai.pro · budget 100 requests
  2. 0.0s✓Resolved www.coronerai.pro → 172.67.194.16 (+3 more), all public
  3. 0.1s▸Probing HTTPS, HTTP and legacy TLS
  4. 0.2s✓GET https://www.coronerai.pro/ → 200 in 112ms
  5. 0.2s·GET http://www.coronerai.pro/ → 301 https://www.coronerai.pro/
  6. 0.2s·TLS 1.0 probe not possible from this network
  7. 0.2s·TLS 1.1 probe not possible from this network
  8. 0.2s·Security headers present: content-security-policy, x-frame-options, x-content-type-options, referrer-policy, permissions-policy
  9. 0.2s·0 cookies set on the homepage
  10. 0.3s▸Reading DNS, security.txt and the page's JavaScript
  11. 0.3s·Homepage references 3 scripts; reading main-CYYqTCr3.js, landing-TQ2axIX-.js, menu-dL-RyBOh.js
  12. 0.4s·security.txt not found (HTTP 404)
  13. 0.4s·DNS: DNSSEC off · CAA none · SPF none · DMARC none
  14. 0.4s·main-CYYqTCr3.js (4 KB)
  15. 0.4s·landing-TQ2axIX-.js (1 KB)
  16. 0.4s·menu-dL-RyBOh.js (3 KB)
  17. 0.4s·No wallet or chain libraries recognised
  18. 0.6s✓Graded C (68/100) · 0 high, 2 medium, 3 low · 17 requests to the target
  19. 0.7s◆Writing summary with openai/gpt-oss-120b
  20. 5.6s◆Summary ready · 5 prioritized fixes

Scope & limitations

Assessment type
Premium, public, non-invasive
Payment
Complimentary
Target
www.coronerai.pro
Final URL
https://www.coronerai.pro/
Resolved addresses
172.67.194.16, 104.21.20.186, 2606:4700:3036::6815:14ba, 2606:4700:3035::ac43:c210
Scanned
Oct 20, 2026, 16:19 UTC
Duration
0.6s
Requests made
17 (budget 100)
Report ID
druy59hg54
  • 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 www.coronerai.pro? 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.