# AIClicks.net Full Technical Reference Updated from verifiable editorial and telemetry sources. AIClicks.net is operated by WolkInc and is distinct from aiclicks.io. # Product and scoring AIClicks provides 14 free focused tools and a multi-module scanner for security, privacy, performance, accessibility, SEO, GEO, AI, post-quantum readiness, and blockchain intelligence. Findings include raw evidence and, where applicable, CVSS 3.1 vectors, CWE identifiers, OWASP mappings, and stack-specific remediation. # Live benchmark Computed: 2026-10-20T00:00:00.000Z Sample size: 1240 Window: 90 days Average score: 68/100 Critical failure rate: 62% Missing HSTS: 37% Missing CSP: 78% No DMARC: 54% JSON: https://aiclicks.net/api/public/benchmark.json CSV: https://aiclicks.net/api/public/benchmark.csv # Published technical check references ## HSTS (HTTP Strict Transport Security) Canonical: https://aiclicks.net/checks/hsts What the HSTS header does, why missing HSTS is flagged as a security finding, and the exact Strict-Transport-Security header to add on nginx, Apache, and Cloudflare. HSTS is an HTTP response header (Strict-Transport-Security) that tells browsers to only ever connect to your site over HTTPS — even if the user types http:// or clicks an old http link. Without it, a single insecure request can be intercepted. Missing HSTS enables SSL-stripping attacks: an attacker on the network downgrades the connection to plain HTTP and reads or modifies traffic. It's also a grading factor in every security scanner and a PCI DSS expectation. Primary specification: https://owasp.org/www-project-secure-headers/ Related tool: https://aiclicks.net/tools/headers-check ## Content-Security-Policy (CSP) Canonical: https://aiclicks.net/checks/content-security-policy What the Content-Security-Policy header does, why it's the highest-impact defense against XSS attacks, and a starter CSP policy you can deploy today. Content-Security-Policy tells the browser exactly which sources are allowed to load scripts, styles, images, and other resources. It's the single most effective defense against cross-site scripting (XSS) — even if an attacker injects code, the browser refuses to run it. XSS remains a top web vulnerability (CWE-79). CSP is defense-in-depth that works when input sanitization fails. Scanners flag its absence because it's the cheapest high-impact header you can add. Primary specification: https://owasp.org/www-project-secure-headers/ Related tool: https://aiclicks.net/tools/headers-check ## DMARC (Domain-based Message Authentication) Canonical: https://aiclicks.net/checks/dmarc What a DMARC record does, why p=none leaves your domain spoofable, and the step-by-step path from monitoring to p=reject enforcement without breaking mail flow. DMARC is a DNS TXT record (_dmarc.yourdomain.com) that tells receiving mail servers what to do with email that fails SPF/DKIM checks: nothing (p=none), quarantine (p=quarantine), or reject (p=reject). It also enables aggregate reports so you can see who's sending as you. Without DMARC at p=reject, anyone can send email as your domain — phishing your customers, partners, and staff. 48% of domains we scan have no DMARC policy at all, meaning they're fully spoofable. Primary specification: https://www.rfc-editor.org/rfc/rfc7489 Related tool: https://aiclicks.net/tools/email-check ## Cookie Consent (GDPR/ePrivacy) Canonical: https://aiclicks.net/checks/cookie-consent What valid cookie consent looks like under GDPR and ePrivacy, why pre-ticked banners and pre-loaded trackers fail compliance, and how to fix your banner. Under GDPR and the ePrivacy Directive, non-essential cookies and trackers (analytics, ads, social pixels) require prior, freely-given, specific consent. That means: no tracking before the user clicks accept, no pre-ticked boxes, and rejecting must be as easy as accepting. 61% of sites we scan load tracking scripts before consent — a direct GDPR violation. EU data protection authorities have issued fines specifically for this pattern. It's also the easiest thing for a competitor or activist to report. Primary specification: https://owasp.org/www-project-secure-headers/ Related tool: https://aiclicks.net/tools/cookie-check ## SPF (Sender Policy Framework) Canonical: https://aiclicks.net/checks/spf What the SPF record does for email authentication, how to publish a correct TXT record for your domain, and the lookup-limit pitfalls that break delivery. SPF is a DNS TXT record listing which mail servers may send email for your domain. Receiving servers check it to reject forgeries from unauthorized hosts. Without SPF, any server on the internet can claim to send as you. It's the first of the three email-authentication pillars (SPF, DKIM, DMARC). Primary specification: https://www.rfc-editor.org/rfc/rfc7208 Related tool: https://aiclicks.net/tools/email-check ## DKIM (DomainKeys Identified Mail) Canonical: https://aiclicks.net/checks/dkim What DKIM email signing does, how it proves your mail wasn't forged or altered, and how to enable it on Google Workspace, Microsoft 365, and other providers. DKIM adds a cryptographic signature to outgoing email. Receivers verify it against your public key in DNS, proving the message wasn't altered and really came from your domain. DKIM survives forwarding better than SPF and is required for DMARC alignment. Without it, your legitimate mail is more likely to be flagged. Primary specification: https://www.rfc-editor.org/rfc/rfc6376 Related tool: https://aiclicks.net/tools/email-check ## X-Frame-Options / frame-ancestors Canonical: https://aiclicks.net/checks/x-frame-options What clickjacking attacks are, how invisible iframes hijack your users' clicks, and the X-Frame-Options and frame-ancestors headers that stop them. X-Frame-Options (or CSP frame-ancestors) controls whether your pages can be embedded in iframes on other sites. Without it, attackers can overlay invisible frames to hijack clicks — 'clickjacking'. Clickjacking turns your trusted UI into an attacker's puppet: users think they're clicking your buttons but act on the attacker's page. One header eliminates the entire class. Primary specification: https://owasp.org/www-project-secure-headers/ Related tool: https://aiclicks.net/tools/headers-check ## llms.txt (AI Crawler Guidance) Canonical: https://aiclicks.net/checks/llms-txt What the llms.txt file is, how it guides AI crawlers like GPTBot and ClaudeBot to cite your site accurately, and why AI visibility starts with crawler guidance. llms.txt is an emerging convention (like robots.txt, but for AI): a markdown file at your domain root describing your site for large language models. It helps AI assistants cite you accurately instead of guessing. AI search is eating traditional search share. Sites with clear llms.txt, accurate structured data, and crawlable content get cited; sites without it get summarized from third-party sources — or ignored. Primary specification: https://owasp.org/www-project-secure-headers/ Related tool: https://aiclicks.net/tools/ai-crawl-check ## TLS 1.3 Handshake Canonical: https://aiclicks.net/checks/tls-1-3-handshake Inspect the negotiated TLS 1.3 protocol, key exchange, cipher, ALPN, and certificate chain with reproducible command-line evidence. A TLS 1.3 handshake is the live negotiation between a client and server that establishes protocol version, cipher suite, key exchange, certificates, and application protocol. Configuration intent is not enough: the edge endpoint must negotiate the expected values. Legacy protocol fallback and weak certificate chains can preserve downgrade or interception risk even when an origin server is configured correctly. Validate every public hostname and CDN edge. Primary specification: https://www.rfc-editor.org/rfc/rfc8446 Related tool: https://aiclicks.net/tools/ssl-check ## ML-KEM Post-Quantum TLS Canonical: https://aiclicks.net/checks/ml-kem-post-quantum-tls Understand hybrid X25519MLKEM768 negotiation, NIST FIPS 203, harvest-now-decrypt-later exposure, and a staged PQC rollout. ML-KEM is the NIST-standardized key-encapsulation mechanism in FIPS 203. In web TLS it is commonly deployed as a hybrid group with X25519 so security does not depend exclusively on either a classical or post-quantum primitive. Long-lived confidential traffic captured today may be decrypted when cryptographically relevant quantum computers exist. Inventory and hybrid negotiation evidence establish a defensible migration baseline. Primary specification: https://www.rfc-editor.org/rfc/rfc8446 Related tool: https://aiclicks.net/tools/ssl-check ## DNSSEC Validation Canonical: https://aiclicks.net/checks/dnssec-validation Validate DS, DNSKEY, RRSIG, denial-of-existence records, and the authenticated-data chain from the root to your zone. DNSSEC adds origin authentication and integrity to DNS through signed records and a chain of trust. A zone is only validated when parent DS records, child DNSKEY records, signatures, algorithms, and timing all align. Broken DNSSEC can make a domain unreachable for validating resolvers, while absent DNSSEC leaves DNS answers vulnerable to cache poisoning and on-path manipulation. Primary specification: https://www.rfc-editor.org/rfc/rfc4033 Related tool: https://aiclicks.net/tools/seo-check ## CAA DNS Record Canonical: https://aiclicks.net/checks/caa-dns-record Control which certificate authorities may issue for a domain and validate issue, issuewild, and incident-reporting parameters. CAA records let domain owners authorize certificate issuers and optionally define wildcard and incident-reporting policy. Certificate authorities must check the relevant CAA set before issuance. A precise CAA policy reduces accidental or unauthorized certificate issuance and creates useful incident signals without replacing certificate transparency monitoring. Primary specification: https://www.rfc-editor.org/rfc/rfc8659 Related tool: https://aiclicks.net/tools/ssl-check ## Permissions-Policy Header Canonical: https://aiclicks.net/checks/permissions-policy-header Restrict camera, microphone, geolocation, payment, and other powerful browser features by origin and iframe. Permissions-Policy is an HTTP response header that defines which origins may use powerful browser capabilities. It applies to the top-level document and delegated iframe contexts. Unneeded capability access expands the impact of third-party compromise and embedded-content mistakes. A deny-by-default policy documents and enforces the intended browser attack surface. Primary specification: https://owasp.org/www-project-secure-headers/ Related tool: https://aiclicks.net/tools/headers-check ## Referrer-Policy Header Canonical: https://aiclicks.net/checks/referrer-policy-header Prevent sensitive path and query leakage while preserving useful same-origin and cross-origin analytics behavior. Referrer-Policy controls how much of the current URL a browser sends in the Referer request header during navigation and subresource fetches. URLs can contain tenant names, internal paths, campaign identifiers, or accidental secrets. A strict policy limits cross-origin leakage while retaining origin-level attribution. Primary specification: https://owasp.org/www-project-secure-headers/ Related tool: https://aiclicks.net/tools/headers-check ## COOP, CORP, and COEP Headers Canonical: https://aiclicks.net/checks/coop-corp-coep-headers Deploy cross-origin isolation safely and understand the interaction among opener, embedder, and resource policies. COOP isolates browsing context groups, COEP controls which cross-origin resources may be embedded, and CORP lets a resource declare which sites may load it. Together they enable cross-origin isolation. These headers reduce cross-window and speculative side-channel exposure, but incomplete deployment can break third-party resources. Inventory dependencies before enforcing isolation. Primary specification: https://owasp.org/www-project-secure-headers/ Related tool: https://aiclicks.net/tools/headers-check ## MTA-STS and TLS-RPT Canonical: https://aiclicks.net/checks/mta-sts-tls-rpt Require authenticated TLS for inbound mail and receive reports when delivery encryption or certificate validation fails. MTA-STS publishes an HTTPS policy telling sending mail servers to require TLS and validate MX identities. TLS-RPT publishes a reporting address for aggregate transport failures. Opportunistic SMTP TLS can be downgraded. MTA-STS closes that gap after a valid policy is cached, while TLS-RPT provides operational evidence needed for safe enforcement. Primary specification: https://www.rfc-editor.org/rfc/rfc8446 Related tool: https://aiclicks.net/tools/email-check ## GPTBot and ClaudeBot robots.txt Rules Canonical: https://aiclicks.net/checks/gptbot-claudebot-robots-txt Write explicit, testable crawler policy for OpenAI, Anthropic, Perplexity, Google, and retrieval user agents. robots.txt applies ordered user-agent groups and path rules. AI training crawlers, search crawlers, and user-triggered retrieval agents often use distinct tokens, so one broad rule may not express the intended policy. Accidental wildcard blocks can remove a site from AI retrieval; accidental allows can conflict with content licensing policy. Explicit groups make governance auditable. Primary specification: https://owasp.org/www-project-secure-headers/ Related tool: https://aiclicks.net/tools/robots-txt-checker ## Schema.org JSON-LD for GEO Canonical: https://aiclicks.net/checks/schema-org-json-ld-geo Create entity-consistent Organization, WebSite, Article, FAQ, Product, and Dataset graphs that match visible content. JSON-LD expresses entities and relationships in a machine-readable graph. For GEO, the highest-value markup identifies the publisher, author, page subject, dates, evidence, and canonical URL without contradicting visible HTML. Invalid or misleading schema is ignored and can create trust risk. Valid markup improves extraction but only when the same facts are present for users on the page. Primary specification: https://owasp.org/www-project-secure-headers/ Related tool: https://aiclicks.net/tools/seo-check # Published compliance and readiness guides ## GDPR Cookie Consent: Practical Compliance Guide Canonical: https://aiclicks.net/guides/gdpr-cookie-consent What EU law actually requires for cookies and trackers under GDPR and ePrivacy — and how to verify your site complies with a free scan. Applies to: Any website serving visitors in the EU/EEA that uses non-essential cookies or trackers (analytics, advertising, social pixels, embedded video). It doesn't matter where your company is based. Requirements: - Prior consent: No non-essential cookies or trackers before the user actively consents. Loading Google Analytics on pageview — before any click — is non-compliant. - Freely given & specific: No pre-ticked boxes. Consent must be opt-in per purpose (necessary, analytics, marketing), not bundled into one 'accept all' with no alternative. - As easy to reject as accept: 'Reject all' must be as prominent as 'Accept all'. Hiding reject behind layers of settings has drawn enforcement action. - Withdrawable: Users must be able to change their mind as easily as they consented — a persistent settings link, not a buried page. - Documented: You must be able to prove when and what each user consented to (consent records). Implementation steps: 1. Run the free cookie checker to see what's loading before consent today. 2. Deploy a consent manager in blocking mode (scripts gated on consent state). 3. Configure per-purpose toggles with reject-as-easy-as-accept. 4. Re-scan to verify zero trackers fire before interaction. 5. Set up monitoring so future deploys don't regress. ## NIS2 Website Security: What It Means in Practice Canonical: https://aiclicks.net/guides/nis2-website-security NIS2's cybersecurity requirements translated into concrete website controls: what the directive demands and the technical checks to prove compliance. Applies to: Essential and important entities under NIS2 — energy, transport, health, finance, digital infrastructure, public administration, and their supply chains — across all EU member states. Requirements: - Risk management measures: Appropriate technical and organizational measures proportional to risk — including vulnerability handling and disclosure. - Incident handling: 24-hour early warning, 72-hour notification, and final report within a month for significant incidents. - Supply-chain security: Security of your suppliers and service providers — including the third-party scripts on your website. - Management accountability: Management bodies must approve and oversee cybersecurity risk management. Fines can target individuals. Implementation steps: 1. Baseline your public attack surface with a full scan. 2. Remediate critical/high findings with the provided fix snippets. 3. Enable continuous monitoring for regression and new exposures. 4. Export PDF reports as audit evidence for your risk register. ## Email Authentication (SPF, DKIM, DMARC): Deployment Guide Canonical: https://aiclicks.net/guides/dmarc-email-security Stop domain spoofing: roll out SPF, DKIM, and DMARC to p=reject without breaking legitimate mail. Applies to: Every domain that sends email — and every domain that doesn't (attackers spoof non-sending domains too). Required or expected by Google/Yahoo bulk-sender rules, PCI DSS 4.0, and an increasing number of procurement checklists. Requirements: - SPF: DNS record authorizing your sending servers. Keep lookups under 10. - DKIM: Cryptographic signatures on outgoing mail, verified via DNS public key. - DMARC: Policy telling receivers what to do with failures — and reports showing who's sending as you. - p=reject: The end state: unauthenticated mail claiming to be you is rejected outright. Implementation steps: 1. Scan your domain free to see current SPF/DKIM/DMARC state. 2. Publish SPF covering all legitimate senders (test with ~all first). 3. Enable DKIM in your mail provider and publish the key. 4. Publish DMARC at p=none with a rua mailbox; review reports for 2 weeks. 5. Move to p=quarantine, then p=reject. ## EU AI Act Transparency: Website & Content Obligations Canonical: https://aiclicks.net/guides/ai-act-transparency What the EU AI Act requires for AI-generated content, chatbots, and transparency on your website — and the disclosure controls to stay compliant. Applies to: Providers and deployers of AI systems in the EU — including websites using AI chatbots, AI-generated content, or AI-driven personalization. Requirements: - AI interaction disclosure: Users must know when they're interacting with AI (chatbots, virtual assistants). - AI-generated content labeling: Synthetic text, images, audio, or video must be labeled as AI-generated in a machine-readable way. - Deepfake safeguards: Additional obligations where synthetic media could deceive. Implementation steps: 1. Inventory every AI touchpoint on your site (chatbots, generated content, recommendations). 2. Add clear, upfront disclosure at each touchpoint. 3. Ensure machine-readable labeling (metadata, watermarks) for synthetic media. 4. Scan to verify transparency signals are present and correct. ## NIST Post-Quantum Migration to 2030 Canonical: https://aiclicks.net/guides/nist-post-quantum-migration-2030 An engineering checklist for FIPS 203, 204, and 205 adoption, hybrid TLS, crypto inventory, and CNSA 2.0 deadlines. Applies to: Security, infrastructure, identity, and procurement teams responsible for data that must remain confidential through the 2030s. Requirements: - Cryptographic inventory: Locate TLS, VPN, code-signing, PKI, firmware, backup, database, and application-layer cryptography with owners and retention periods. - Hybrid transition: Test hybrid classical plus ML-KEM key establishment before relying on post-quantum primitives alone. - Algorithm agility: Remove hard-coded algorithm assumptions and establish tested rollover procedures for keys, certificates, and libraries. Implementation steps: 1. Classify data by confidentiality lifetime and harvest-now-decrypt-later exposure. 2. Inventory every externally negotiated algorithm and certificate chain. 3. Pilot hybrid ML-KEM with measurable compatibility and latency budgets. 4. Require PQC roadmaps and SBOM evidence from critical vendors. 5. Re-test quarterly and after every edge, TLS, or PKI change. ## PCI DSS 4.0 HTTP Headers and CSP Canonical: https://aiclicks.net/guides/pci-dss-4-0-http-headers-csp Translate PCI DSS 4.0 requirements 6.4.3 and 11.6.1 into payment-page script inventory, authorization, integrity, and change detection. Applies to: Merchants and service providers with payment pages, embedded payment frames, checkout scripts, or responsibility for e-commerce client-side security. Requirements: - Script inventory: Maintain an authorized inventory of payment-page scripts with business justification and ownership. - Integrity: Use CSP, SRI where feasible, and controlled loading paths to detect or prevent unauthorized script modification. - Change detection: Monitor payment-page headers and script surfaces at the frequency required by your assessed implementation. Implementation steps: 1. Map every payment page and third-party script. 2. Deploy a report-only CSP and resolve legitimate violations. 3. Authorize scripts explicitly and add SRI for stable external assets. 4. Monitor response headers and page changes with retained alerts. 5. Provide assessors the inventory, approvals, and before/after evidence. ## SOC 2 Website Security Evidence Canonical: https://aiclicks.net/guides/soc2-website-security-evidence Build repeatable technical evidence for change management, vulnerability management, monitoring, and incident-response controls. Applies to: SaaS engineering and security teams preparing for SOC 2 Type II readiness or operating-period evidence collection. Requirements: - Repeatability: Evidence must identify scope, time, operator or automation, expected control, observed result, and exception handling. - Operating effectiveness: One screenshot proves design at a moment; recurring timestamped checks help demonstrate operation across the review period. - Exception workflow: Link failed checks to owners, risk decisions, remediation commits, and retest evidence. Implementation steps: 1. Map public controls to your control matrix and system description. 2. Capture a baseline scan with raw evidence. 3. Schedule monitoring at a frequency justified by risk. 4. Route exceptions into ticketing with owners and due dates. 5. Export samples across the audit period and reconcile gaps. # API Documentation: https://aiclicks.net/api Scanner endpoint: POST https://aiclicks.net/api/v1/scans/url Reports are evidence-based decision support, not legal proof of security, authorship, fraud, or compliance.