Security - https://duckduckgo.com BeaverCheck Audit

D

Cross-Origin Tab Safety

Action

22 of 68 new-tab link(s) missing rel=noopener

FIX

22 of 68 new-tab link(s) missing rel=noopener

22 link(s) open in a new tab without rel=noopener

Without rel="noopener", the destination tab can navigate the original tab via window.opener -- a reverse-tabnabbing phishing primitive. Modern browsers default to noopener since Chrome 88 / Firefox 79 / Safari 12.1, but explicit rel="noopener noreferrer" remains the documented best practice for older browsers, in-app webviews, and security scanners.

F

Permissions-Policy Granularity

Action

0% high-risk feature coverage (0/10)

FIX

0% high-risk feature coverage (0/10)

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

The Permissions-Policy header explicitly declares policies for 0/10 high-risk features. Covered: Not declared (default-allow): camera, microphone, geolocation, 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: 0% (0/10)

B

Security Headers

6 of 10 headers properly configured

REVIEW

6 of 10 headers properly configured

HSTS is missing includeSubDomains

Without includeSubDomains, subdomains can still be accessed over HTTP.

Got: max-age=31536000 Expected: max-age=31536000; includeSubDomains

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options is properly configured

Got: SAMEORIGIN

Referrer-Policy has a weak value

Got: origin Expected: strict-origin-when-cross-origin

Permissions-Policy is set

Got: interest-cohort=()

Content-Security-Policy is present

Got: default-src 'none' ; connect-src https://duck.ai https://*.duck.ai https://duck…

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

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

Without includeSubDomains, subdomains can still be accessed over HTTP.

Expected: max-age=31536000; includeSubDomains

Why this matters

Without includeSubDomains, a forgotten dev subdomain over HTTP can set malicious cookies that ride to the apex.

Learn more ▾

HSTS without includeSubDomains protects only the exact domain. Cookies set on a non-HSTS subdomain can ride to the apex via cookie-scope attacks. The fix is one directive append. Verify all subdomains support HTTPS first — adding includeSubDomains to a domain with HTTP-only subdomains breaks them.

Source: RFC 6797

Expected: strict-origin-when-cross-origin

Why this matters

Weak Referrer-Policy values leak full URLs (with query params, tokens, IDs) to every third-party resource on the page.

Learn more ▾

Default referrer behavior shares the full referring URL with images, scripts, and other resources from third-party origins. If your URLs contain tokens, session IDs, or user emails (in query strings or paths), every third-party tracker gets them. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter).

Source: MDN Referrer-Policy / W3C

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

C

Content Security Policy

Action

6 of 10 CSP checks passed

REVIEW

6 of 10 CSP checks passed

Raw CSP policy

Got: default-src 'none' ; connect-src https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com ; manifest-src https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com ; media-src https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com ; script-src blob: https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com 'unsafe-inline' 'unsafe-eval' ; font-src data: https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com ; img-src data: https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com ; style-src https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com 'unsafe-inline' ; object-src 'none' ; worker-src blob: ; child-src blob: https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com ; frame-src blob: https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com ; form-action https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com ; frame-ancestors 'self' https://html.duckduckgo.com; base-uri 'self' ; block-all-mixed-content ;

default-src directive is set

Got: default-src 'none'

'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 blob: https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com 'unsafe-inline' 'unsafe-eval'

'unsafe-eval' found in script source

'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.

Got: script-src blob: https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com 'unsafe-inline' 'unsafe-eval'

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 'self' https://html.duckduckgo.com

form-action directive is set

Got: form-action https://duck.ai https://*.duck.ai https://duckduckgo.com https://*.duckduckgo.com https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/ https://spreadprivacy.com

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

'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.

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

connect-src https://duck.aihttps://*.duck.aihttps://duckduckgo.comhttps://*.duckduckgo.comhttps://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/https://spreadprivacy.com

manifest-src https://duck.aihttps://*.duck.aihttps://duckduckgo.comhttps://*.duckduckgo.comhttps://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/https://spreadprivacy.com

media-src https://duck.aihttps://*.duck.aihttps://duckduckgo.comhttps://*.duckduckgo.comhttps://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/https://spreadprivacy.com

script-src blob:https://duck.aihttps://*.duck.aihttps://duckduckgo.comhttps://*.duckduckgo.comhttps://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/https://spreadprivacy.com'unsafe-inline''unsafe-eval'

font-src data:https://duck.aihttps://*.duck.aihttps://duckduckgo.comhttps://*.duckduckgo.comhttps://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/https://spreadprivacy.com

img-src data:https://duck.aihttps://*.duck.aihttps://duckduckgo.comhttps://*.duckduckgo.comhttps://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/https://spreadprivacy.com

style-src https://duck.aihttps://*.duck.aihttps://duckduckgo.comhttps://*.duckduckgo.comhttps://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/https://spreadprivacy.com'unsafe-inline'

object-src 'none'

worker-src blob:

child-src blob:https://duck.aihttps://*.duck.aihttps://duckduckgo.comhttps://*.duckduckgo.comhttps://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/https://spreadprivacy.com

frame-src blob:https://duck.aihttps://*.duck.aihttps://duckduckgo.comhttps://*.duckduckgo.comhttps://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/https://spreadprivacy.com

form-action https://duck.aihttps://*.duck.aihttps://duckduckgo.comhttps://*.duckduckgo.comhttps://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/https://spreadprivacy.com

frame-ancestors 'self'https://html.duckduckgo.com

base-uri 'self'

block-all-mixed-content

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

security.txt

Vulnerability disclosure policy

REVIEW

Vulnerability disclosure policy

security.txt found

Got: https://duckduckgo.com/security.txt

security.txt: Missing required 'Contact' field

security.txt: Missing required 'Expires' field (RFC 9116)

security.txt

B

CSP Inline-Style Readiness

8 inline style attribute(s) detected

REVIEW

8 inline style attribute(s) detected

Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 8 inline style(s) is low. Affected element types include: span, div, h1. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.

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.

B

Referrer-Policy Strictness

Referrer-Policy is `origin` (moderate -- origin always, never path)

REVIEW

Referrer-Policy is `origin` (moderate -- origin always, never path)

Referrer-Policy: `origin` -- moderate -- origin always, never path

Sends only the origin on EVERY request (same-origin and cross-origin). Loses the ability to track specific landing pages via Referer; gains uniform privacy. Weaker privacy than `strict-origin` because origin still leaks on HTTPS-to-HTTP.

Got: origin

C

Permissions-Policy

Action

1 directives, 5 missing

REVIEW

1 directives, 5 missing

interest-cohort=() — blocked for all origins

camera not restricted

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

microphone not restricted

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

geolocation not restricted

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

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

interest-cohort=()

Feature Permissions

Blocked Self Only Unrestricted Not Set

interest-cohort Blocked

camera Not Set

microphone Not Set

geolocation Not Set

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+

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_256_GCM_SHA384

HTTP/2 is not negotiated

HTTP/2 provides multiplexing and header compression for better performance.

Got: http/1.1

OCSP stapling enabled

Certificate is valid (expires in 178 days)

Got: 2026-11-19T23:59:59Z

Certificate chain has 3 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 2 domain(s)

Got: *.duckduckgo.com, duckduckgo.com

Certificate is issued by a trusted CA

Got: CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.

Learn more ▾

HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.

Source: MDN Web Docs

Connection

Protocol

TLS 1.3

Cipher Suite

TLS_AES_256_GCM_SHA384

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=*.duckduckgo.com,O=Duck Duck Go\, Inc.,L=Paoli,ST=Pennsylvania,C=USIssuer CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=USValid 2026-05-05T00:00:00Z → 2026-11-19T23:59:59ZExpires in 178 days SANs *.duckduckgo.com, duckduckgo.comSignature SHA256-RSASerial 6e833ecb16bfc5f76ff025ce93d898e

Intermediate (CA Certificate)

Subject CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=USIssuer CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2021-03-30T00:00:00Z → 2031-03-29T23:59:59ZExpires in 1769 days Signature SHA256-RSASerial cf5bd062b5602f47ab8502c23ccf066

Intermediate (CA Certificate)

Subject CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USIssuer CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2013-08-01T12:00:00Z → 2038-01-15T12:00:00ZExpires in 4253 days Signature SHA256-RSASerial 33af1e6a711a9a0bb2864b11d09fae5

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+

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+

Source Map Exposure

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

PASS

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

No source maps accessible across 10 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+

Subdomain Inventory Exposure

No risky subdomain names in certificate SANs

PASS

No risky subdomain names in certificate SANs

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

Potential exposures found

PASS

Potential exposures found

/phpinfo.php is publicly accessible

Debug or admin endpoint is accessible. This may expose server internals or provide attack vectors.

No security.txt found

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

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	✗ Exposed	Debug	Warning
/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+

Email Security

DMARC: reject, SPF: -all, DKIM, TLS-RPT

PASS

DMARC: reject, SPF: -all, DKIM, TLS-RPT

DMARC policy is reject — strongest protection

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

DKIM configured (selectors: selector1, 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 configured

Got: mailto:n1um42s6@tls.us.dmarcian.com

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 reject — strongest protection Record v=DMARC1; p=reject; pct=100; rua=mailto:n1um42s6@ag.dmarcian.com

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

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.

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) not advertised

HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.

HSTS enabled (base policy)

HSTS missing includeSubDomains

Without includeSubDomains, HSTS only protects the exact domain.

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