Security - https://www.ndmnet.eu BeaverCheck Audit

D

Permissions-Policy Granularity

Action

30% high-risk feature coverage (3/10)

FIX

30% high-risk feature coverage (3/10)

Permissions-Policy covers 3/10 high-risk features (30%)

The Permissions-Policy header explicitly declares policies for 3/10 high-risk features. Covered: camera, microphone, geolocation Not declared (default-allow): payment, usb, serial, midi, accelerometer, gyroscope, magnetometer The non-declared features fall back to their spec-default policy (usually `self`), which means an XSS-injected or compromised iframe could request them. For features the page genuinely doesn't use, declare `feature=()` to fully close them.

Got: 30% (3/10)

F

Email Security

Action

no DMARC, SPF: ~all

FIX

no DMARC, SPF: ~all

No DMARC record found

Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.

SPF ends in ~all (soft fail)

Soft fail tells receivers to accept-but-mark unauthorized mail. Migrate to -all once you've confirmed all legitimate senders are listed (DMARC aggregate reports help verify).

No DKIM detected via common selectors

DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.

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

No DMARC record found

Without DMARC, email receivers have no policy for handling authentication failures from your domain.

Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.

Why this matters

Without DMARC, anyone can send phishing emails using your domain name.

Learn more ▾

DMARC tells receiving mail servers what to do with email that fails SPF/DKIM checks for your domain. With a strict 'p=reject' policy, spoofed emails get bounced; without it they reach the inbox. Domains used in phishing campaigns lose deliverability and brand trust fast.

Source: DMARC.org / NIST

Soft fail tells receivers to accept-but-mark unauthorized mail. Migrate to -all once you've confirmed all legitimate senders are listed (DMARC aggregate reports help verify).

Why this matters

Informational: a labeled value pair from the audit.

DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.

Why this matters

No DKIM signature on outbound mail — receivers can't cryptographically prove the message came from your domain.

Learn more ▾

DKIM signs outbound mail with a private key whose public half lives in DNS at <selector>._domainkey.<domain>. Without DKIM, DMARC alone can't tell legitimate mail from spoofs, and large mailbox providers (Gmail, Yahoo) increasingly require DKIM for inbox placement. Note: this check probes a curated list of common selectors; non-standard selectors produce a false negative.

Source: RFC 6376 / Google + Yahoo 2024 sender requirements

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

WAF / Bot Protection

No WAF detected via response headers

REVIEW

No WAF detected via response headers

No WAF detected

Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.

B

Subdomain Inventory Exposure

2 risky subdomain name(s) in certificate SANs

REVIEW

2 risky subdomain name(s) in certificate SANs

2 risky subdomain name(s) advertised in certificate SANs

These names are publicly visible via Certificate Transparency logs (crt.sh, censys.io) -- any attacker can enumerate them in seconds. Operators are often unaware that internal/staging/admin endpoints are inadvertently advertised this way. Mitigation: use a wildcard cert that doesn't enumerate, issue per-environment certs without non-prod SANs on the prod cert, or move internal services to private DNS off the public cert.

Got: webmail.ndmnet.eu, webmail.sgdm.it

B

Permissions-Policy

3 directives, 2 missing

REVIEW

3 directives, 2 missing

geolocation=() — blocked for all origins

microphone=() — blocked for all origins

camera=() — blocked for all origins

payment not restricted

Consider adding payment=() to block payment access from embedded content.

usb not restricted

Consider adding usb=() to block usb access from embedded content.

Raw Header

geolocation=() microphone=() camera=()

Feature Permissions

Blocked Self Only Unrestricted Not Set

geolocation Blocked

microphone Blocked

camera Blocked

payment Not Set

usb Not Set

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

Security Headers

8 of 10 headers properly configured

PASS

8 of 10 headers properly configured

Strict-Transport-Security is properly configured (consider adding preload)

Got: max-age=31536000; includeSubDomains

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 is set

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

Content-Security-Policy is present

Got: default-src 'none'; connect-src 'self'; script-src 'self' 'sha256-+SiyWl9zb54aQF…

Cross-Origin-Opener-Policy header is missing

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

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: LiteSpeed

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

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin

Why this matters

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Learn more ▾

Cross-Origin-Opener-Policy: same-origin prevents cross-origin pages from sharing a browsing-context group with yours. This blocks cross-window references that enable Spectre-style timing attacks and tab-nabbing. Required if you want to enable SharedArrayBuffer.

Source: MDN / web.dev

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

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

A+

Content Security Policy

8 of 10 CSP checks passed

PASS

8 of 10 CSP checks passed

Raw CSP policy

Got: default-src 'none'; connect-src 'self'; script-src 'self' 'sha256-+SiyWl9zb54aQF/t6ZprIlk1kCXBlSvnOZoU9lNoBL4=' 'sha256-1PBNd/1/p/PvPbjywRwR80LM2v/btOb/Y/eKBK2zJps=' 'sha256-1ln2f709Gw/+8wErl/4xxDztDEe8hHlsyZkFOrmZuxs=' 'sha256-9VICfBoF3OmTNu6ocbYsg8nzpPBYXAMZBlW+RsN3tEc=' 'sha256-Vt+v8BQO3iNYdrO48AvXrDyvpokkqn9MAoJveeJOeEE=' 'sha256-X+FqUzoZlZnBgUAMOdUvwNAfgguxETxiuFrhXoGBwsM=' 'sha256-boDhT8YYEBwQS4hpChKyxWntRwrzwE85PVutPhZrmGo=' 'sha256-c61wYvlJfIVu6xw7iNGC4AuC+oXZRD3FCigu3BrHZrs=' 'sha256-hvxJ9cw64T0SFd1D3lzE+Pk6NuqbybLKw4iPlDItHf4=' 'sha256-mXult69KnR2WQmWEZVC9SZAI/j7/fcvm3Vyo95chzMI=' 'sha256-vH9u/aLyz3KA8HGV9gqBFxVEij48OmKMRUd4jDsmZFk=' 'sha256-zCQ9QbpGD2bNmh08yV4v405/uygkkd5JPaQIffu2/2U='; style-src 'self'; img-src 'self' data:; font-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; require-trusted-types-for 'script'; trusted-types ndmnet-modal

default-src directive is set

Got: default-src 'none'

No 'unsafe-inline' in script source

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

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 'none'

connect-src 'self'

script-src 'self''sha256-+SiyWl9zb54aQF/t6ZprIlk1kCXBlSvnOZoU9lNoBL4=''sha256-1PBNd/1/p/PvPbjywRwR80LM2v/btOb/Y/eKBK2zJps=''sha256-1ln2f709Gw/+8wErl/4xxDztDEe8hHlsyZkFOrmZuxs=''sha256-9VICfBoF3OmTNu6ocbYsg8nzpPBYXAMZBlW+RsN3tEc=''sha256-Vt+v8BQO3iNYdrO48AvXrDyvpokkqn9MAoJveeJOeEE=''sha256-X+FqUzoZlZnBgUAMOdUvwNAfgguxETxiuFrhXoGBwsM=''sha256-boDhT8YYEBwQS4hpChKyxWntRwrzwE85PVutPhZrmGo=''sha256-c61wYvlJfIVu6xw7iNGC4AuC+oXZRD3FCigu3BrHZrs=''sha256-hvxJ9cw64T0SFd1D3lzE+Pk6NuqbybLKw4iPlDItHf4=''sha256-mXult69KnR2WQmWEZVC9SZAI/j7/fcvm3Vyo95chzMI=''sha256-vH9u/aLyz3KA8HGV9gqBFxVEij48OmKMRUd4jDsmZFk=''sha256-zCQ9QbpGD2bNmh08yV4v405/uygkkd5JPaQIffu2/2U='

style-src 'self'

img-src 'self'data:

font-src 'self'

form-action 'self'

base-uri 'self'

object-src 'none'

frame-ancestors 'none'

require-trusted-types-for 'script'

trusted-types ndmnet-modal

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 75 days)

Got: 2026-11-04T19:55:28Z

Certificate chain has 3 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 18 domain(s)

Got: cpanel.ndmnet.eu, cpanel.sgdm.it, cpcalendars.ndmnet.eu, cpcalendars.sgdm.it, cpcontacts.ndmnet.eu, cpcontacts.sgdm.it, mail.ndmnet.eu, mail.sgdm.it, ndmnet.eu, sgdm.it, sgdm.ndmnet.eu, webdisk.ndmnet.eu, webdisk.sgdm.it, webmail.ndmnet.eu, webmail.sgdm.it, www.ndmnet.eu, www.sgdm.it, www.sgdm.ndmnet.eu

Certificate is issued by a trusted CA

Got: CN=YR1,O=Let's Encrypt,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=cpcalendars.sgdm.itIssuer CN=YR1,O=Let's Encrypt,C=USValid 2026-08-06T19:55:29Z → 2026-11-04T19:55:28ZExpires in 75 days SANs cpanel.ndmnet.eu, cpanel.sgdm.it, cpcalendars.ndmnet.eu, cpcalendars.sgdm.it, cpcontacts.ndmnet.eu, cpcontacts.sgdm.it, mail.ndmnet.eu, mail.sgdm.it, ndmnet.eu, sgdm.it, sgdm.ndmnet.eu, webdisk.ndmnet.eu, webdisk.sgdm.it, webmail.ndmnet.eu, webmail.sgdm.it, www.ndmnet.eu, www.sgdm.it, www.sgdm.ndmnet.euSignature SHA256-RSASerial 6e3197f7d907ab06fc65c7304ac0b370171

Intermediate (CA Certificate)

Subject CN=YR1,O=Let's Encrypt,C=USIssuer CN=Root YR,O=ISRG,C=USValid 2025-09-03T00:00:00Z → 2028-09-02T23:59:59ZExpires in 743 days Signature SHA256-RSASerial a20253f15f2691c05dc1ce13b9bcca4e

Intermediate (CA Certificate)

Subject CN=Root YR,O=ISRG,C=USIssuer CN=ISRG Root X1,O=Internet Security Research Group,C=USValid 2026-05-13T00:00:00Z → 2032-09-02T23:59:59ZExpires in 2204 days Signature SHA256-RSASerial f24b6d17f9d9ad7cb1c9fea78782699f

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+

security.txt

Vulnerability disclosure policy

PASS

Vulnerability disclosure policy

security.txt found

Got: https://www.ndmnet.eu/.well-known/security.txt

security.txt

Contact: mailto:info@ndmnet.eu

Expires: 2027-08-11T00:00:00Z

Policy: https://www.ndmnet.eu/.well-known/security.txt

A+

Cross-Origin Tab Safety

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

PASS

All 4 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+

Trusted Types (XSS Sink Hardening)

Trusted Types enforced for 'script'

PASS

Trusted Types enforced for 'script'

Trusted Types enforced via require-trusted-types-for 'script'

Got: default-src 'none'; connect-src 'self'; script-src 'self' 'sha256-+SiyWl9zb54aQF/t6ZprIlk1kCXBlSvnOZoU9lNoBL4=' 'sha256-1PBNd/1/p/PvPbjywRwR80LM2v/btOb/Y/eKBK2zJps=' 'sha256-1ln2f709Gw/+8wErl/4xxDztDEe8hHlsyZkFOrmZuxs=' 'sha256-9VICfBoF3OmTNu6ocbYsg8nzpPBYXAMZBlW+RsN3tEc=' 'sha256-Vt+v8BQO3iNYdrO48AvXrDyvpokkqn9MAoJveeJOeEE=' 'sha256-X+FqUzoZlZnBgUAMOdUvwNAfgguxETxiuFrhXoGBwsM=' 'sha256-boDhT8YYEBwQS4hpChKyxWntRwrzwE85PVutPhZrmGo=' 'sha256-c61wYvlJfIVu6xw7iNGC4AuC+oXZRD3FCigu3BrHZrs=' 'sha256-hvxJ9cw64T0SFd1D3lzE+Pk6NuqbybLKw4iPlDItHf4=' 'sha256-mXult69KnR2WQmWEZVC9SZAI/j7/fcvm3Vyo95chzMI=' 'sha256-vH9u/aLyz3KA8HGV9gqBFxVEij48OmKMRUd4jDsmZFk=' 'sha256-zCQ9QbpGD2bNmh08yV4v405/uygkkd5JPaQIffu2/2U='; style-src 'self'; img-src 'self' data:; font-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; require-trusted-types-for 'script'; trusted-types ndmnet-modal

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+

Subresource Integrity Adoption

Page has no third-party scripts or stylesheets -- SRI not applicable

PASS

Page has no third-party scripts or stylesheets -- SRI not applicable

No third-party scripts or stylesheets to protect with SRI

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+

Source Map Exposure

No source maps accessible (probed 1 candidate URL(s))

PASS

No source maps accessible (probed 1 candidate URL(s))

No source maps accessible across 1 probed candidate(s)

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+

Subresource Integrity

No external resources

PASS

No external resources

No external resources to protect

SRI Coverage No external resources — SRI not applicable

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

security.txt is present — good practice

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	✗ Exposed	Security Policy	Info
/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)

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