This Cookie Policy explains how dnssec.me uses cookies, local storage, and similar technologies when you read DNSSEC guides, browse the blog, or use interactive checklists where available. Read it together with our Privacy Policy, which covers personal data you send via contact forms.
1. What technologies we use
Cookies are small text files placed on your device. We may also use localStorage to remember your cookie consent decision across pages so long tutorials are not interrupted by repeated prompts. Session identifiers can help keep multi-step lab-style pages coherent during a single visit.
2. Why dnssec.me needs cookies
Our audience includes operators who jump between long-form troubleshooting articles. Cookies help us deliver pages efficiently through CDN-friendly patterns, protect forms from simple automated abuse, and—only with permission—understand which topics (for example chain-of-trust failures versus key rollover) need clearer diagrams.
3. Consent and legal bases
Where regulations require consent for non-essential cookies, we display a banner allowing you to accept or decline optional analytics. Strictly necessary cookies that are essential to provide the service you request (security, load distribution, remembering your choice) may be used under applicable exemptions. You may withdraw optional consent by clearing site data and returning to dnssec.me.
4. Categories
Strictly necessary. Support basic security, maintain continuity during navigation across deep-linked anchor sections, store consent state, and mitigate scripted form spam at a minimal level.
Analytics (optional). If enabled, collect aggregated metrics such as page views, approximate scroll engagement, referral source, device category, and coarse region derived from IP. We use this to prioritize updates to validation guides when resolver behavior shifts.
Functional. Remember minor UI preferences for the duration of a session when implemented (for example expanded glossary panels).
Advertising. We do not operate third-party behavioral advertising networks on dnssec.me as a standard configuration. Campaign experiments will be disclosed here if they introduce such tags.
5. Third-party content
Embedded code samples hosted on external platforms or iframes may set their own cookies when you interact with them. We do not control those technologies.
6. Retention
Session cookies expire when you close the browser. Persistent cookies or local storage entries typically expire within twelve months unless you remove them sooner.
7. Browser controls
You can delete cookies per site, block third-party cookies, or use private browsing. Aggressive blocking may require you to reconfirm preferences more often. Industry ad opt-out pages primarily address ad networks.
8. Global visitors
Readers from the EEA, UK, Switzerland, and similar regions receive disclosures consistent with transparency and consent rules for non-essential cookies, alongside our Privacy Policy.
9. Children
The Site targets technical professionals. We do not knowingly use cookies to market to children.
10. Updates
When our tracking technologies change, we will revise this policy and the date above.
11. Contact
Questions: [email protected]. Related: Terms of Service.