Security - https://aif.ru BeaverCheck Audit

F

Security Headers

Action

3 of 10 headers properly configured

FIX

3 of 10 headers properly configured

HSTS header is missing

Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.

Expected: max-age=31536000; includeSubDomains

X-Content-Type-Options header is missing

This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.

Expected: nosniff

X-Frame-Options header is missing

This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.

Expected: DENY

Referrer-Policy header is missing

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: 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: upgrade-insecure-requests;

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: ddos-guard

Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.

Expected: max-age=31536000; includeSubDomains

Why this matters

Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.

Learn more ▾

HSTS tells browsers 'never speak HTTP to this domain again.' Without it, a network attacker (public WiFi, malicious ISP, hostile DNS) intercepts the first HTTP attempt and serves a downgraded version of your site. One header, big surface reduction.

Source: RFC 6797 / OWASP

This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.

Expected: nosniff

Why this matters

MIME sniffing lets browsers run uploaded files as JavaScript, turning a file upload into an XSS.

Learn more ▾

Setting X-Content-Type-Options: nosniff tells browsers to trust your declared Content-Type instead of guessing. Without it, an attacker who uploads a polyglot file can sometimes get it executed as a script. One header, no downside.

Source: OWASP / MDN

This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.

Expected: DENY

Why this matters

Without frame protection, your site can be embedded in a hostile page and used for clickjacking.

Learn more ▾

Clickjacking overlays your site under a transparent malicious page so users click invisible buttons. Setting X-Frame-Options: DENY (or a modern frame-ancestors CSP directive) blocks the embedding entirely. There's almost never a legitimate reason to allow it.

Source: OWASP / MDN

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin

Why this matters

Default browser behavior leaks full URLs (including query params and tokens) to every third-party resource — set a strict policy.

Learn more ▾

Without a Referrer-Policy header, browsers send the full referring URL with images, scripts, and fonts loaded from third-party origins. URLs containing tokens, user IDs, or session params end up in third-party logs. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter) to limit leakage.

Source: MDN / W3C

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

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

D

Cookie Security

Action

4 cookies analyzed, 1 checks passed

FIX

4 cookies analyzed, 1 checks passed

Cookie '__ddg8_' is missing the Secure flag

Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.

Cookie '__ddg8_' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie '__ddg8_' has no SameSite attribute

Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

Cookie '__ddg10_' is missing the Secure flag

Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.

Cookie '__ddg10_' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie '__ddg10_' has no SameSite attribute

Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

Cookie '__ddg9_' is missing the Secure flag

Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.

Cookie '__ddg9_' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie '__ddg9_' has no SameSite attribute

Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

Cookie '__ddg1_' is missing the Secure flag

Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.

Cookie '__ddg1_' has the HttpOnly flag

Cookie '__ddg1_' has no SameSite attribute

Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

4 cookies analyzed 4 critical 7 warnings

Name	Secure	HttpOnly	SameSite	Size	Issues
__ddg8_	✗	✗	—	23 B	3
__ddg10_	✗	✗	—	18 B	3
__ddg9_	✗	✗	—	22 B	3
__ddg1_	✗	✓	—	27 B	2

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=()

D

security.txt

Action

No /.well-known/security.txt published

FIX

security.txt

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

C

Content Security Policy

Action

2 of 10 CSP checks passed

REVIEW

2 of 10 CSP checks passed

Raw CSP policy

Got: upgrade-insecure-requests;

default-src directive is missing

default-src provides a fallback for other directives. Set it to restrict default resource loading.

Expected: default-src 'self'

No script-src or default-src to check for 'unsafe-inline'

No script-src or default-src to check for 'unsafe-eval'

No script-src or default-src to check for wildcard

object-src falls back to default-src

base-uri directive is missing

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'

frame-ancestors directive is missing

frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.

Expected: frame-ancestors 'self'

form-action directive is missing

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'

upgrade-insecure-requests is enabled

default-src provides a fallback for other directives. Set it to restrict default resource loading.

Expected: default-src 'self'

Why this matters

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

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'

Why this matters

Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.

Learn more ▾

A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.

Source: MDN CSP

frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.

Expected: frame-ancestors 'self'

Why this matters

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

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'

Why this matters

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

Parsed Policy

upgrade-insecure-requests

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

B

Transport Security

HTTP/3, HSTS, and TLS version analysis

REVIEW

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.

Missing Strict-Transport-Security header

HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.

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

A+

TLS & Certificates

TLS 1.3, 7 checks passed

PASS

TLS 1.3, 7 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 not negotiated

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

Got: http/1.1

Certificate is valid (expires in 314 days)

Got: 2027-03-03T07:41:29Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 5 domain(s)

Got: *.aif.ru, autodiscover.aif.ru, mail.aif.ru, owa.aif.ru, aif.ru

Certificate is issued by a trusted CA

Got: CN=GlobalSign RSA OV SSL CA 2018,O=GlobalSign nv-sa,C=BE

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_128_GCM_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=*.aif.ru,O=Argumenty i Fakty,L=Moscow,ST=Moscow,C=RUIssuer CN=GlobalSign RSA OV SSL CA 2018,O=GlobalSign nv-sa,C=BEValid 2026-01-30T07:41:30Z → 2027-03-03T07:41:29ZExpires in 314 days SANs *.aif.ru, autodiscover.aif.ru, mail.aif.ru, owa.aif.ru, aif.ruSignature SHA256-RSASerial 21c68f0e450d6d4570ba218a

Intermediate (CA Certificate)

Subject CN=GlobalSign RSA OV SSL CA 2018,O=GlobalSign nv-sa,C=BEIssuer CN=GlobalSign,OU=GlobalSign Root CA - R3,O=GlobalSignValid 2018-11-21T00:00:00Z → 2028-11-21T00:00:00ZExpires in 943 days Signature SHA256-RSASerial 1ee5f221dfc623bd4333a8557

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

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	—

A

Email Security

DMARC: quarantine

PASS

DMARC: quarantine

DMARC policy is quarantine — good protection

DMARC

Policy quarantine — good protection Record v=DMARC1;p=quarantine