Security - https://startrekonline.info BeaverCheck Audit

F

Subresource Integrity Adoption

Action

0% SRI adoption (0/4 third-party resources)

FIX

0% SRI adoption (0/4 third-party resources)

SRI adoption: 0/4 third-party resources protected (0%)

Of 4 third-party `<script>` / `<link rel=stylesheet>` resources, 0 (0%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource. Missing SRI on (first 4 examples): - https://cdn.logr-in.com/logger-1.min.js - https://cdn-cookieyes.com/client_data/6216d01ca9478d1601e2fd4a/script.js - https://kit.fontawesome.com/5812c6b103.js - https://cdn-cookieyes.com/client_data/6216d01ca9478d1601e2fd4a/banner.js Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.

Got: 0% (0/4)

D

Source Map Exposure

Action

2 publicly-accessible source map(s) -- full source code leaked

FIX

2 publicly-accessible source map(s) -- full source code leaked

2 publicly-accessible JavaScript source map(s)

Source maps (.js.map files) reveal the original source code -- variable names, comments, file structure, and sometimes secrets that were stripped from the bundled output. They're shipped to production by mistake almost universally; the standard fix is a build-tool config flag (Webpack: `devtool: false` or `'hidden-source-map'`; Vite: `build.sourcemap: false`; Next.js: `productionBrowserSourceMaps: false`). Once removed, audit your CDN/edge cache to evict any previously-cached .map URLs. Sample accessible URLs: https://startrekonline.info/polyfills-JM43HSLT.js.map, https://startrekonline.info/main-2HNOKNKR.js.map.

F

Subresource Integrity

Action

0 of 4 external resources have SRI

FIX

0 of 4 external resources have SRI

External script from cdn.logr-in.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://cdn.logr-in.com/logger-1.min.js

External script from cdn-cookieyes.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://cdn-cookieyes.com/client_data/6216d01ca9478d1601e2fd4a/script.js

External script from kit.fontawesome.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://kit.fontawesome.com/5812c6b103.js

External script from cdn-cookieyes.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://cdn-cookieyes.com/client_data/6216d01ca9478d1601e2fd4a/banner.js

SRI Coverage 0 / 4 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	cdn.logr-in.com	✗ Missing
<script>	cdn-cookieyes.com	✗ Missing
<script>	kit.fontawesome.com	✗ Missing
<script>	cdn-cookieyes.com	✗ Missing

D

Permissions-Policy

Action

No header set

FIX

No header set

No Permissions-Policy header

Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

No Permissions-Policy header set.

Without this header, embedded iframes can request access to sensitive device features.

Suggested header

Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=()

B

Security Headers

7 of 10 headers properly configured

REVIEW

7 of 10 headers properly configured

HSTS is enabled with preload

Got: max-age=31536000; includeSubDomains; preload

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options is properly configured

Got: DENY

Referrer-Policy is properly configured

Got: strict-origin-when-cross-origin

Permissions-Policy header is missing

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()

Content-Security-Policy is present

Got: default-src 'self'; img-src 'self' data: blob: https://cdn.startrekonline.info c…

Cross-Origin-Opener-Policy is set but not 'same-origin'

Got: same-origin-allow-popups Expected: same-origin

Cross-Origin-Embedder-Policy header is missing

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

X-Powered-By header is not present

Server header is present without version info

Got: cloudflare

Domain is not in the Chrome HSTS preload list (status: unknown)

Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

Got: unknown

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()

Why this matters

Permissions-Policy locks down browser APIs you don't use — without it, every page can request camera/mic/geolocation if XSS lands.

Learn more ▾

By default every page can request the camera, microphone, geolocation, payment APIs, and dozens more. Permissions-Policy turns off the ones you don't need so a future bug can't quietly start using them. It's a defense-in-depth header — one line, big surface reduction.

Source: MDN / W3C

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

Why this matters

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Learn more ▾

Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.

Source: MDN / web.dev

Expected: same-origin

Why this matters

COOP is set to a less-restrictive value (same-origin-allow-popups or unsafe-none) — partial isolation only.

Learn more ▾

COOP: same-origin is the strictest level. same-origin-allow-popups allows authenticated popup windows back to your origin. unsafe-none is the legacy default (effectively off). Pick the strictest level your app's popup flows tolerate.

Source: MDN COOP

Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

Why this matters

Not in the Chrome preload list — first-time visitors over plain HTTP can be downgraded by a network attacker before HSTS kicks in.

Learn more ▾

The HSTS header only protects users who have already visited the site (TOFU window). Adding your domain to the Chrome preload list closes that gap so HSTS is enforced from the very first connection. Requires a preload-ready header (max-age=31536000+, includeSubDomains, preload) then submission at hstspreload.org. Inclusion ships in the next Chrome release after acceptance.

Source: hstspreload.org

B

Content Security Policy

7 of 10 CSP checks passed

REVIEW

7 of 10 CSP checks passed

Raw CSP policy

Got: default-src 'self'; img-src 'self' data: blob: https://cdn.startrekonline.info cdn-cookieyes.com www.googletagmanager.com; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://cdn-cookieyes.com https://www.googletagmanager.com https://cdn.logrocket.io https://cdn.lr-ingest.io https://cdn.lr-in.com https://cdn.lr-in-prod.com https://cdn.lr-ingest.com https://cdn.ingest-lr.com https://cdn.lr-intake.com https://cdn.intake-lr.com https://cdn.logr-ingest.com https://cdn.lrkt-in.com https://cdn.logr-in.com https://static.cloudflareinsights.com https://kit.fontawesome.com; style-src 'self' 'unsafe-inline' https://fonts.gstatic.com https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; object-src 'none'; frame-src 'self' https://kit.fontawesome.com https://www.youtube-nocookie.com; child-src 'self' blob:; form-action 'self'; frame-ancestors 'none'; base-uri 'self'; manifest-src 'self'; media-src 'self'; worker-src 'self' blob:; connect-src 'self' https://api.startrekonline.info https://cdn.startrekonline.info *.cookieyes.com cdn-cookieyes.com google-analytics.com *.google-analytics.com https://*.logrocket.io https://*.lr-ingest.io https://*.logrocket.com https://*.lr-in.com https://*.lr-in-prod.com https://*.lr-ingest.com https://*.ingest-lr.com https://*.lr-intake.com https://*.intake-lr.com https://*.logr-ingest.com https://*.lrkt-in.com https://*.logr-in.com https://static.cloudflareinsights.com https://o4510795012374528.ingest.de.sentry.io https://ka-p.fontawesome.com;

default-src directive is set

Got: default-src 'self'

'unsafe-inline' found in script source

'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.

Got: script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://cdn-cookieyes.com https://www.googletagmanager.com https://cdn.logrocket.io https://cdn.lr-ingest.io https://cdn.lr-in.com https://cdn.lr-in-prod.com https://cdn.lr-ingest.com https://cdn.ingest-lr.com https://cdn.lr-intake.com https://cdn.intake-lr.com https://cdn.logr-ingest.com https://cdn.lrkt-in.com https://cdn.logr-in.com https://static.cloudflareinsights.com https://kit.fontawesome.com

No 'unsafe-eval' in script source

No wildcard in script source

object-src is set to 'none'

Got: object-src 'none'

base-uri is properly restricted

Got: base-uri 'self'

frame-ancestors directive is set

Got: frame-ancestors 'none'

form-action directive is set

Got: form-action 'self'

upgrade-insecure-requests is not set

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.

Why this matters

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Learn more ▾

unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.

Source: OWASP CSP / MDN

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

Why this matters

Without upgrade-insecure-requests, any HTTP subresource link survives as a mixed-content warning instead of auto-upgrading.

Learn more ▾

Adding `upgrade-insecure-requests` to your CSP turns every http:// subresource fetch into https:// at the browser layer. One-line defense against accidental mixed content from legacy links or third-party widgets.

Source: MDN CSP

Parsed Policy

default-src 'self'

img-src 'self'data:blob:https://cdn.startrekonline.infocdn-cookieyes.comwww.googletagmanager.com

script-src 'self''unsafe-inline''wasm-unsafe-eval'https://cdn-cookieyes.comhttps://www.googletagmanager.comhttps://cdn.logrocket.iohttps://cdn.lr-ingest.iohttps://cdn.lr-in.comhttps://cdn.lr-in-prod.comhttps://cdn.lr-ingest.comhttps://cdn.ingest-lr.comhttps://cdn.lr-intake.comhttps://cdn.intake-lr.comhttps://cdn.logr-ingest.comhttps://cdn.lrkt-in.comhttps://cdn.logr-in.comhttps://static.cloudflareinsights.comhttps://kit.fontawesome.com

style-src 'self''unsafe-inline'https://fonts.gstatic.comhttps://fonts.googleapis.com

font-src 'self'https://fonts.gstatic.comdata:

object-src 'none'

frame-src 'self'https://kit.fontawesome.comhttps://www.youtube-nocookie.com

child-src 'self'blob:

form-action 'self'

frame-ancestors 'none'

base-uri 'self'

manifest-src 'self'

media-src 'self'

worker-src 'self'blob:

connect-src 'self'https://api.startrekonline.infohttps://cdn.startrekonline.info*.cookieyes.comcdn-cookieyes.comgoogle-analytics.com*.google-analytics.comhttps://*.logrocket.iohttps://*.lr-ingest.iohttps://*.logrocket.comhttps://*.lr-in.comhttps://*.lr-in-prod.comhttps://*.lr-ingest.comhttps://*.ingest-lr.comhttps://*.lr-intake.comhttps://*.intake-lr.comhttps://*.logr-ingest.comhttps://*.lrkt-in.comhttps://*.logr-in.comhttps://static.cloudflareinsights.comhttps://o4510795012374528.ingest.de.sentry.iohttps://ka-p.fontawesome.com

C

security.txt

Action

No security.txt file found

REVIEW

No security.txt file found

security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field.

Expected: /.well-known/security.txt

security.txt

No security.txt found at /.well-known/security.txt

B

Trusted Types (XSS Sink Hardening)

Trusted Types not enabled

REVIEW

Trusted Types not enabled

Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode.

C

Permissions-Policy Granularity

Action

No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin

REVIEW

No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin

Permissions-Policy header not set -- features default to allow-on-same-origin

Without a `Permissions-Policy` (or legacy `Feature-Policy`) header, every powerful browser feature defaults to its spec default policy (typically `self`). A third-party iframe injected via XSS or a misconfigured embed can still request access to the user's camera, microphone, geolocation, payment APIs, USB devices, etc. Explicitly deny features the page doesn't need: ``` Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=() ``` Features the page legitimately uses can stay enabled with `feature=(self)`.

Got: header absent

B

Email Security

DMARC: quarantine, SPF: -all, DKIM

REVIEW

DMARC: quarantine, SPF: -all, DKIM

DMARC policy is quarantine — good protection

SPF ends in -all (hard fail) — strongest setting

DKIM configured (selectors: selector2, selector1, s2, s1)

MTA-STS not configured

MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.

TLS-RPT not configured

TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.

BIMI not configured

BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

DMARC

Policy quarantine — good protection Record v=DMARC1; p=quarantine; rua=mailto:6381dcd8c1244a0ea9047e8e3bb33cb4@dmarc-reports.cloudflare.net

MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.

Why this matters

Without MTA-STS, inbound mail can be silently downgraded to plain SMTP by a network attacker.

Learn more ▾

MTA-STS (RFC 8461) tells sending mail servers to use TLS and to refuse delivery if TLS fails. Requires both a TXT record at _mta-sts.<domain> AND a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt. Without it, an active attacker on the network path can strip STARTTLS and read the email in plaintext.

Source: RFC 8461

TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.

Why this matters

Without TLS-RPT, you have no visibility into inbound TLS failures — MTA-STS misconfigurations stay hidden until users complain.

Learn more ▾

TLS-RPT (RFC 8460) is the feedback channel for MTA-STS: senders post aggregate reports of TLS-handshake failures to the URI in your _smtp._tls TXT record. Without it, an MTA-STS misconfiguration silently rejects mail and you find out only when someone notices missing email.

Source: RFC 8460

BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

B

CORS Configuration

No CORS headers

REVIEW

No CORS headers

No CORS headers present — secure default

CORS Configuration ✓ Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control

A+

TLS & Certificates

TLS 1.3, 8 checks passed

PASS

TLS 1.3, 8 checks passed

TLS 1.3 is used

Got: TLS 1.3

Strong cipher suite is used

Got: TLS_AES_128_GCM_SHA256

HTTP/2 is negotiated

Got: h2

OCSP stapling not enabled

Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.

Certificate is valid (expires in 67 days)

Got: 2026-11-15T05:18:38Z

Certificate chain has 3 certificates

Certificate uses modern signature algorithm

Got: ECDSA-SHA256

Certificate covers 1 domain(s)

Got: startrekonline.info

Certificate is issued by a trusted CA

Got: CN=WE1,O=Google Trust Services,C=US

Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.

Why this matters

Without OCSP stapling, every first-time visitor pays an extra OCSP roundtrip — and the CA learns who's visiting your site.

Learn more ▾

OCSP stapling has the server fetch its own revocation status from the CA and attach the signed response to the TLS handshake. Without it, browsers contact the CA directly: extra latency for the user and a privacy leak (the CA sees who connected). Enable ssl_stapling on (nginx) / SSLUseStapling On (Apache) / OCSPStapling = on (Caddy auto-enables).

Source: RFC 6961 / Mozilla Server-Side TLS guide

Connection

Protocol

TLS 1.3

Cipher Suite

TLS_AES_128_GCM_SHA256

HTTP Version

h2 (HTTP/2)

Certificate Chain

Leaf Certificate

Subject CN=startrekonline.infoIssuer CN=WE1,O=Google Trust Services,C=USValid 2026-08-17T04:18:43Z → 2026-11-15T05:18:38ZExpires in 67 days SANs startrekonline.infoSignature ECDSA-SHA256Serial d580da3ffc04858d0ecab1ab0302b07e

Intermediate (CA Certificate)

Subject CN=WE1,O=Google Trust Services,C=USIssuer CN=GTS Root R4,O=Google Trust Services LLC,C=USValid 2023-12-13T09:00:00Z → 2029-02-20T14:00:00ZExpires in 895 days Signature ECDSA-SHA384Serial 7ff31977972c224a76155d13b6d685e3

Intermediate (CA Certificate)

Subject CN=GTS Root R4,O=Google Trust Services LLC,C=USIssuer CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BEValid 2023-11-15T03:43:21Z → 2028-01-28T00:00:42ZExpires in 505 days Signature SHA256-RSASerial 7fe530bf331343bedd821610493d8a1b

A+

Cookie Security

No cookies set — no cookie security risks

PASS

No cookies set — no cookie security risks

No cookies detected — no cookie security risks to report.

A+

Cookie Hygiene

No cookies set -- cookie-hygiene check is N/A

PASS

No cookies set -- cookie-hygiene check is N/A

No cookies set

A

WAF / Bot Protection

Cloudflare

PASS

Cloudflare

Cloudflare detected

Detected via: cf-ray: a382ccdc9c2a0cd3-CDG

Got: Cloudflare

A+

Cross-Origin Tab Safety

All 3 new-tab link(s) carry rel=noopener

PASS

All 3 new-tab link(s) carry rel=noopener

A+

CSP Inline-Style Readiness

No inline style attributes -- strict CSP is feasible

PASS

No inline style attributes -- strict CSP is feasible

No inline style attributes detected

A+

Bot Challenge Detection

Scan reached real page content (no bot-protection interstitial)

PASS

Scan reached real page content (no bot-protection interstitial)

No bot-protection interstitial detected -- the rest of the report reflects the real page

A+

Soft-404 Detection

No soft-404 patterns detected in page title or headings

PASS

No soft-404 patterns detected in page title or headings

A+

Empty Page Detection

Page has substantive body text and no placeholder / template-leak signals

PASS

Page has substantive body text and no placeholder / template-leak signals

A+

Geo-Restriction Detection

No geo-restriction signals detected -- scan reached the page from an allowed region

PASS

No geo-restriction signals detected -- scan reached the page from an allowed region

No geo-restriction detected

A+

Maintenance Mode Detection

No maintenance-mode signals detected -- scan reached a normal page

PASS

No maintenance-mode signals detected -- scan reached a normal page

No maintenance-mode signals detected

A+

CORS Depth

No CORS response headers -- the resource is same-origin-only by browser default

PASS

No CORS response headers -- the resource is same-origin-only by browser default

A+

Referrer-Policy Strictness

Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)

PASS

Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)

Referrer-Policy: `strict-origin-when-cross-origin` -- modern default -- full URL same-origin, origin-only cross-origin

The modern browser default (Chrome 85+, Firefox 87+, Safari 15+). Full URL Referer on same-origin; origin only on cross-origin; no Referer on HTTPS-to-HTTP downgrade. Privacy-safe and breaks no analytics. The recommended explicit value.

Got: strict-origin-when-cross-origin

A+

HTML Version Disclosure

No software-version disclosures in HTML

PASS

No software-version disclosures in HTML

A+

Open Redirect Surface

No redirect-shaped query parameters in DOM links

PASS

No redirect-shaped query parameters in DOM links

A+

Auth Security

Page is not a login form -- auth-security checks are N/A

PASS

Page is not a login form -- auth-security checks are N/A

Page does not appear to be a login form

A+

Subdomain Inventory Exposure

No risky subdomain names in certificate SANs

PASS

No risky subdomain names in certificate SANs

A+

JS Library Vulnerabilities

No known vulnerabilities

PASS

No known vulnerabilities

No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+

Information Leakage

No exposures

PASS

No exposures

No security.txt found

Consider adding a security.txt at /.well-known/security.txt.

No sensitive files exposed

No sensitive files exposed — all paths returned 404.

Path	Status	Category	Risk
/.git/HEAD	✓ Not found	Version Control	—
/.git/config	✓ Not found	Version Control	—
/.svn/entries	✓ Not found	Version Control	—
/.env	✓ Not found	Configuration	—
/.env.local	✓ Not found	Configuration	—
/.env.production	✓ Not found	Configuration	—
/wp-config.php	✓ Not found	Configuration	—
/.htaccess	✓ Not found	Configuration	—
/phpinfo.php	✓ Not found	Debug	—
/server-status	✓ Not found	Debug	—
/server-info	✓ Not found	Debug	—
/.well-known/security.txt	✓ Not found	Security Policy	—
/package.json	✓ Not found	dependency-manifest	—
/composer.json	✓ Not found	dependency-manifest	—
/Gemfile	✓ Not found	dependency-manifest	—
/Gemfile.lock	✓ Not found	dependency-manifest	—
/requirements.txt	✓ Not found	dependency-manifest	—
/pom.xml	✓ Not found	dependency-manifest	—
/.gitlab-ci.yml	✓ Not found	ci-config	—
/.travis.yml	✓ Not found	ci-config	—

A+

API Surface

No API specs or GraphQL introspection found (probed 11 candidate path(s))

PASS

No API specs or GraphQL introspection found (probed 11 candidate path(s))

No API specs or GraphQL introspection found (probed 11 path(s))

A+

Transport Security

HTTP/3, HSTS, and TLS version analysis

PASS

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) supported

The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.

HSTS enabled (includeSubDomains, preload)

HSTS preload enabled

TLS 1.3 in use (fastest handshake, 1-RTT)