Skip to content
https://alltaxbooks.com

Security

· 32 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
95
GRADE
A
FIX
1
REVIEW
3
PASS
28
INFO
0
Checks
32
28 PASS 3 REVIEW 1 FIX
D
Email Security
Action
no DMARC, SPF: ~all, DKIM, TLS-RPT
FIX
no DMARC, SPF: ~all, DKIM, TLS-RPT
Warning::
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.
Info::
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).
Info::
DKIM configured (selectors: default, google)
Warning::
MTA-STS DNS record present but policy file missing
The _mta-sts TXT record exists but the policy file at the mta-sts subdomain is unreachable. Senders cannot enforce MTA-STS without both.
Info::
TLS-RPT configured
Got: mailto:office@alltaxbooks.com
Info::
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

The _mta-sts TXT record exists but the policy file at the mta-sts subdomain is unreachable. Senders cannot enforce MTA-STS without both.

Why this matters

MTA-STS is half-deployed — senders see the TXT record but can't fetch the policy, so enforcement falls back to opportunistic TLS.

Learn more ▾

Both halves are required: the _mta-sts TXT record (versioned policy ID) AND the policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt. Publish the policy file and verify it returns 200 with Content-Type: text/plain.

Source: RFC 8461 §3

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.

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
Info::
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.
C
security.txt
Action
No security.txt file found
REVIEW
No security.txt file found
Info::
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
CORS Configuration
No CORS headers
REVIEW
No CORS headers
Info::
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
10 of 10 headers properly configured
PASS
10 of 10 headers properly configured
Info::
HSTS is enabled with preload
Got: max-age=63072000; includeSubDomains; preload
Info::
X-Content-Type-Options is properly configured
Got: nosniff
Info::
X-Frame-Options is properly configured
Got: DENY
Info::
Referrer-Policy is properly configured
Got: strict-origin-when-cross-origin
Info::
Permissions-Policy is set
Got: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=(), magnetometer=(), serial=(), midi=(), browsing-topics=()
Info::
Content-Security-Policy is present
Got: default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; …
Info::
Cross-Origin-Opener-Policy is properly configured
Got: same-origin
Info::
Cross-Origin-Embedder-Policy is set
Got: require-corp
Info::
X-Powered-By header is not present
Info::
Server header is present without version info
Got: Netlify
Info::
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

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
9 of 10 CSP checks passed
PASS
9 of 10 CSP checks passed
Info::
Raw CSP policy
Got: default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; frame-src 'none'; media-src 'none'; script-src 'self' 'sha256-GYjMLja202p+uU61Z9nh6ywI6hguBWxmIegqbJtaZzE=' 'sha256-uX4d3wLNYRiEeJjnhgkWaVbMWqGXwy7ljSLvBSPpreg='; script-src-attr 'none'; style-src 'self'; style-src-attr 'none'; img-src 'self' data:; font-src 'self'; connect-src 'self' https://*.sharepoint.com https://*.1drv.com https://*.up.1drv.com https://*.officeapps.live.com; form-action 'self' https://formsubmit.co; manifest-src 'self'; worker-src 'self'; upgrade-insecure-requests; require-trusted-types-for 'script'; trusted-types 'none'
Info::
default-src directive is set
Got: default-src 'self'
Info::
No 'unsafe-inline' in script source
Info::
No 'unsafe-eval' in script source
Info::
No wildcard in script source
Info::
object-src is set to 'none'
Got: object-src 'none'
Info::
base-uri is properly restricted
Got: base-uri 'self'
Info::
frame-ancestors directive is set
Got: frame-ancestors 'none'
Info::
form-action directive is set
Got: form-action 'self' https://formsubmit.co
Info::
upgrade-insecure-requests is enabled

Parsed Policy

default-src 'self'
base-uri 'self'
object-src 'none'
frame-ancestors 'none'
frame-src 'none'
media-src 'none'
script-src 'self''sha256-GYjMLja202p+uU61Z9nh6ywI6hguBWxmIegqbJtaZzE=''sha256-uX4d3wLNYRiEeJjnhgkWaVbMWqGXwy7ljSLvBSPpreg='
script-src-attr 'none'
style-src 'self'
style-src-attr 'none'
img-src 'self'data:
font-src 'self'
connect-src 'self'https://*.sharepoint.comhttps://*.1drv.comhttps://*.up.1drv.comhttps://*.officeapps.live.com
form-action 'self'https://formsubmit.co
manifest-src 'self'
worker-src 'self'
upgrade-insecure-requests
require-trusted-types-for 'script'
trusted-types 'none'
A+
TLS & Certificates
TLS 1.3, 8 checks passed
PASS
TLS 1.3, 8 checks passed
Info::
TLS 1.3 is used
Got: TLS 1.3
Info::
Strong cipher suite is used
Got: TLS_AES_128_GCM_SHA256
Info::
HTTP/2 is negotiated
Got: h2
Info::
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.
Info::
Certificate is valid (expires in 51 days)
Got: 2026-11-19T11:32:07Z
Info::
Certificate chain has 4 certificates
Info::
Certificate uses modern signature algorithm
Got: ECDSA-SHA384
Info::
Certificate covers 2 domain(s)
Got: *.alltaxbooks.com, alltaxbooks.com
Info::
Certificate is issued by a trusted CA
Got: CN=YE2,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=alltaxbooks.comIssuer CN=YE2,O=Let's Encrypt,C=USValid 2026-08-21T11:32:08Z → 2026-11-19T11:32:07ZExpires in 51 days SANs *.alltaxbooks.com, alltaxbooks.comSignature ECDSA-SHA384Serial 5390e7e7c13ab7eac126f93ce1f49a1f826
Intermediate (CA Certificate)
Subject CN=YE2,O=Let's Encrypt,C=USIssuer CN=Root YE,O=ISRG,C=USValid 2025-09-03T00:00:00Z → 2028-09-02T23:59:59ZExpires in 705 days Signature ECDSA-SHA384Serial 4df3b15dd6c0784c507cd37b58e6f115
Intermediate (CA Certificate)
Subject CN=Root YE,O=ISRG,C=USIssuer CN=ISRG Root X2,O=Internet Security Research Group,C=USValid 2026-05-13T00:00:00Z → 2032-09-02T23:59:59ZExpires in 2166 days Signature ECDSA-SHA384Serial 872165fc34b6e5fba8add5b3705fb53a
Intermediate (CA Certificate)
Subject CN=ISRG Root X2,O=Internet Security Research Group,C=USIssuer CN=ISRG Root X1,O=Internet Security Research Group,C=USValid 2026-05-13T00:00:00Z → 2032-09-02T23:59:59ZExpires in 2166 days Signature SHA256-RSASerial 6c8f1dc727c7117f7baf853ac980f9cd
A+
Cookie Security
No cookies set — no cookie security risks
PASS
No cookies set — no cookie security risks
Info::
No cookies set — no cookie security risks

No cookies detected — no cookie security risks to report.

A+
Cross-Origin Tab Safety
All 2 new-tab link(s) carry rel=noopener
PASS
All 2 new-tab link(s) carry rel=noopener
Info::
All 2 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
Info::
No inline style attributes detected
A+
Trusted Types (XSS Sink Hardening)
Trusted Types enforced for 'script'
PASS
Trusted Types enforced for 'script'
Info::
Trusted Types enforced via require-trusted-types-for 'script'
Got: default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; frame-src 'none'; media-src 'none'; script-src 'self' 'sha256-GYjMLja202p+uU61Z9nh6ywI6hguBWxmIegqbJtaZzE=' 'sha256-uX4d3wLNYRiEeJjnhgkWaVbMWqGXwy7ljSLvBSPpreg='; script-src-attr 'none'; style-src 'self'; style-src-attr 'none'; img-src 'self' data:; font-src 'self'; connect-src 'self' https://*.sharepoint.com https://*.1drv.com https://*.up.1drv.com https://*.officeapps.live.com; form-action 'self' https://formsubmit.co; manifest-src 'self'; worker-src 'self'; upgrade-insecure-requests; require-trusted-types-for 'script'; trusted-types 'none'
A+
Bot Challenge Detection
Scan reached real page content (no bot-protection interstitial)
PASS
Scan reached real page content (no bot-protection interstitial)
Info::
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
Info::
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
Info::
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
Info::
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
Info::
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
Info::
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
Info::
No CORS response headers -- the resource is same-origin-only by browser default
A+
Permissions-Policy Granularity
100% high-risk feature coverage (10/10)
PASS
100% high-risk feature coverage (10/10)
Info::
Permissions-Policy covers 10/10 high-risk features (100%)
The Permissions-Policy header explicitly declares policies for 10/10 high-risk features. Covered: camera, microphone, geolocation, payment, usb, serial, midi, accelerometer, gyroscope, magnetometer Not declared (default-allow): 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: 100% (10/10)
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)
Info::
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))
Info::
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
Info::
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
Info::
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
Info::
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
Info::
No risky subdomain names in certificate SANs
A+
Subresource Integrity
No external resources
PASS
No external resources
Info::
No external resources to protect
SRI Coverage No external resources — SRI not applicable
A+
JS Library Vulnerabilities
No known vulnerabilities
PASS
No known vulnerabilities
Info::
No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+
Information Leakage
No exposures
PASS
No exposures
Info::
No security.txt found
Consider adding a security.txt at /.well-known/security.txt.
Info::
No sensitive files exposed

No sensitive files exposed — all paths returned 404.

PathStatusCategoryRisk
/.git/HEAD✓ Not foundVersion Control—
/.git/config✓ Not foundVersion Control—
/.svn/entries✓ Not foundVersion Control—
/.env✓ Not foundConfiguration—
/.env.local✓ Not foundConfiguration—
/.env.production✓ Not foundConfiguration—
/wp-config.php✓ Not foundConfiguration—
/.htaccess✓ Not foundConfiguration—
/phpinfo.php✓ Not foundDebug—
/server-status✓ Not foundDebug—
/server-info✓ Not foundDebug—
/.well-known/security.txt✓ Not foundSecurity Policy—
/package.json✓ Not founddependency-manifest—
/composer.json✓ Not founddependency-manifest—
/Gemfile✓ Not founddependency-manifest—
/Gemfile.lock✓ Not founddependency-manifest—
/requirements.txt✓ Not founddependency-manifest—
/pom.xml✓ Not founddependency-manifest—
/.gitlab-ci.yml✓ Not foundci-config—
/.travis.yml✓ Not foundci-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))
Info::
No API specs or GraphQL introspection found (probed 11 path(s))
A+
Permissions-Policy
11 directives, 0 missing
PASS
11 directives, 0 missing
Info::
camera=() — blocked for all origins
Info::
microphone=() — blocked for all origins
Info::
geolocation=() — blocked for all origins
Info::
payment=() — blocked for all origins
Info::
usb=() — blocked for all origins
Info::
accelerometer=() — blocked for all origins
Info::
gyroscope=() — blocked for all origins
Info::
magnetometer=() — blocked for all origins
Info::
serial=() — blocked for all origins
Info::
midi=() — blocked for all origins
Info::
browsing-topics=() — blocked for all origins

Raw Header

camera=() microphone=() geolocation=() payment=() usb=() accelerometer=() gyroscope=() magnetometer=() serial=() midi=() browsing-topics=()

Feature Permissions

Blocked Self Only Unrestricted Not Set
camera Blocked
microphone Blocked
geolocation Blocked
payment Blocked
usb Blocked
accelerometer Blocked
gyroscope Blocked
magnetometer Blocked
serial Blocked
midi Blocked
browsing-topics Blocked
A
Transport Security
HTTP/3, HSTS, and TLS version analysis
PASS
HTTP/3, HSTS, and TLS version analysis
Info::
HTTP/3 (QUIC) not advertised
HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
Info::
HSTS enabled (includeSubDomains, preload)
Info::
HSTS preload enabled
Info::
TLS 1.3 in use (fastest handshake, 1-RTT)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback