Privacy-Engine & Editorial Integrity
IncogSay provides enterprise-tier network diagnostics and calculators without user accounts, query storage, or paywalls. This page documents our technical architecture, editorial review standards, and data-handling commitments in plain language.
01Founding Mission
IncogSay was built on a single premise: the tools that network engineers, security researchers, and privacy-conscious developers need every day should be available instantly, for free, without query surveillance.
Every major tool category on IncogSay — email authentication diagnostics (SPF, DKIM, DMARC, BIMI), URL redirect tracing, SSL/TLS certificate inspection, domain age lookups, and calculators — is provided with no registration requirement, no paywall, and no server-side logging of what you check.
We do not monetise private user query inputs. We do not sell data to brokers. To keep every tool 100% free and maintain our global edge infrastructure, IncogSay is supported by standard, non-intrusive programmatic advertising via Google AdSense, as detailed in our Privacy Policy.
02Zero-Log Technical Architecture
IncogSay tools operate in two execution modes depending on the computation required:
Client-Side JavaScript Execution
Tools performing deterministic arithmetic — all age calculators, date calculators, subnet CIDR calculators, and unit converters — execute entirely inside your browser's JavaScript runtime. No data leaves your device. No network request is made. The computation runs locally with zero server involvement.
Stateless Edge Network Lookups
Tools requiring live DNS resolution, TLS handshake inspection, or HTTP redirect tracing operate through ephemeral, stateless serverless functions deployed at the network edge. Each invocation is isolated: no persistent memory, no query log, no session binding. The function executes, delivers its result, and discards all intermediate state.
In neither execution mode does IncogSay write your query domain, URL, or IP address to any persistent storage system. Edge function invocation logs, if retained by the infrastructure provider at all, contain only standard HTTP metadata (status code, latency, region) — not your query payload.
03RFC Protocol Verification Cycle
Every tool on IncogSay that interprets an internet standard is benchmarked against the canonical RFC or equivalent authoritative specification. This is an engineering discipline enforced during development and quarterly review — not a marketing claim.
| Tool | Primary Standard | Supplementary References |
|---|---|---|
| SPF Checker | RFC 7208 — Sender Policy Framework | RFC 5321 (SMTP), RFC 5322 (Internet Message Format) |
| DKIM Checker | RFC 6376 — DomainKeys Identified Mail | RFC 8301 (SHA-256 key sizes), RFC 8463 (Ed25519) |
| DMARC Checker | RFC 7489 — DMARC | RFC 8616 (EAI), DMARC.org specifications |
| BIMI Checker | BIMI Group Working Group Specification | RFC 3207 (STARTTLS), VMC certificate standards |
| SSL / TLS Inspector | RFC 8446 — TLS 1.3 | CA/Browser Forum Baseline Requirements v2.0, RFC 5280 (X.509) |
| Redirect Tracer | RFC 9110 — HTTP Semantics | RFC 9112 (HTTP/1.1), RFC 7231 |
| Domain Age Checker | RFC 9083 — RDAP JSON Responses | ICANN RDAP Bootstrap Registry, RFC 7482 |
| Subnet Calculator | RFC 4632 — CIDR Address Assignment | RFC 1918 (Private Space), RFC 3021 (/31 Links), RFC 4291 (IPv6) |
When a protocol standard is updated or superseded, IncogSay's tool documentation and algorithm interpretations are reviewed and updated accordingly. This review cycle runs quarterly or whenever a material RFC update is published.
04Editorial Review Standards
All explanatory content on IncogSay — tool documentation, FAQ answers, security risk descriptions, and protocol guides — is written by practising software engineers and reviewed by a technical specialist before publication. Every technical claim must be traceable to a primary source: an RFC, IANA registry, CA/Browser Forum specification, or primary vendor security advisory.
Generic marketing language and thin definitional content are rejected during review. Every page passes an internal technical accuracy check before indexing.
Alex Vance — Lead Technical Reviewer
Alex is a network security architect with expertise in decentralised systems, email authentication protocol stacks (SPF/DKIM/DMARC/BIMI), TLS certificate lifecycle management, and zero-trust network perimeter design. He benchmarks IncogSay's diagnostic engines against IETF drafts, NIST SP 800-series frameworks, and ICANN registrar documentation to ensure complete accuracy.
05Data Handling Commitments
The domains, URLs, passwords, email headers, or calculation dates you enter are processed in-memory or in-browser and immediately discarded. Nothing is logged to a database.
Every tool operates without requiring sign-up, email submission, or any form of identity capture.
We do not broker, sell, or rent user data to third parties. We collect minimal technical telemetry necessary to operate and monetize free web access.
IncogSay is funded by standard programmatic display advertising via Google AdSense, ensuring free access for all users worldwide with full cookie opt-out options.
For network lookups, queries are issued in real time from stateless edge functions and discarded immediately after the response is delivered to your browser.
Every protocol interpreted by an IncogSay tool is verified against its primary IETF RFC or equivalent authoritative specification on a quarterly review cycle.