How DNA handles your site’s traffic.

These are the answers a security review usually asks for, all in one place.

Where DNA runs

Where does DNA sit?: In front of your site, in one of two ways. Point your nameservers at DNA and it answers for your domain from 300+ locations worldwide. Or add the DNA middleware to the code you deploy on Vercel, Cloudflare or nginx.
Does DNA slow my site down?: Barely. DNA answers from 300+ locations worldwide, whichever is closest to your site. The middleware waits at most the cutoff you set, 2 seconds by default, and slower checks run after your page has been sent.

What does DNA keep about each visit?: The page path without its query string, the user agent, whether the request was signed and with which key, and what DNA decided. When a person approves a payment, DNA also keeps the full address of the page they paid for.
Do you store visitors’ IP addresses?: No. DNA keeps a salted, shortened hash of the address, and the address itself is never stored.
Do you store my pages?: No. DNA keeps only each response’s status code, content type and size, so your dashboard can show response times and errors. Your page content is never stored.
How long do you keep visit records?: For retention, compliance certifications and a status page, ask us and we’ll walk your security review through all three.

What if DNA doesn’t answer in time?: Your site keeps serving. If DNA hasn’t answered within your cutoff, the visit goes through as usual. You can set the middleware to block those visits instead, and a visit carrying a payment gets an error rather than a free page.
Who serves my DNS?: With nameservers, DNA serves your domain’s DNS from 300+ locations, email included, so your domain resolves through DNA. To keep your current DNS host, add the DNA middleware instead.
How do I send every visit through DNA?: With nameservers, set your server to accept traffic only from DNA, so nobody can reach it by its own address. Or add the DNA middleware instead.

Will DNA stop anything without my asking?: No. A newly connected site has no rules, so DNA lets every visit through until you ask it to stop something. Search engines and people in browsers go through as before.
Who writes the rules?: You do, under Rules in the dashboard. A new rule starts in testing, so you see what it would have stopped or charged before it does. Or tell us what to stop, and D3 staff write the rule for your site.
How does DNA know an agent is who it says it is?: It checks the agent’s signature against its maker’s keys, or its address against the addresses its maker publishes. Only an agent that passes gets the tag . A name in the user agent is never enough on its own.
How do I leave?: Switch your nameservers back to the ones you had before, or remove the middleware from your code.
Who makes DNA?: D3 Global, Inc., the company behind d3.com.

DNA is free for every site.

For an answer that isn’t here, write to hello@d3.com.