Security at Domain Pilot
Last updated: February 24, 2026
Your credentials enter a vault, not a database.
Domain Pilot connects to your registrar accounts via API. That means you're trusting us with sensitive credentials. We take that seriously. Here's exactly how we protect them.
Zero-Knowledge Encryption
We can't see your API keys. That's not a limitation. It's by design.
When you save a registrar API key in Domain Pilot, it's encrypted using AES-256-GCM before it ever reaches our servers. Your account password is the encryption key. This means your credentials are encrypted on your device before they're transmitted and stored.
The result: even our own team cannot view, access, or retrieve your API keys in plain text. If someone gained access to our database, all they would find is encrypted data that's useless without your password.
Your credentials are only decrypted temporarily, in isolated environments, when Domain Pilot makes an authorized API call to your registrar. Once the call is complete, the decrypted credentials are immediately purged from memory.
What this means for you: You are the only person who can access your registrar credentials. Not us. Not our engineers. Not anyone.
What Happens If You Lose Your Password
Because we use zero-knowledge encryption, your account password is the only key to your stored API credentials. If you lose your password and can't recover it through our password reset process, we cannot retrieve your encrypted API keys for you. You would need to re-enter your registrar API keys after regaining access to your account.
This isn't a flaw. It's proof that the zero-knowledge model works. If we could recover your credentials for you, it would mean we had access to them in the first place.
Encryption at Every Layer
In transit: All communication between your browser and our servers is encrypted using TLS 1.2 or higher. Every API call, every page load, every notification.
At rest: All sensitive data stored in our databases is encrypted using AES-256, the same standard used by financial institutions and government agencies.
API credentials: Encrypted client-side with your password-derived key before transmission. Stored separately from encryption keys. Decrypted only in memory during active API operations.
Infrastructure Security
Hosting: Domain Pilot runs on secure cloud infrastructure with industry-leading providers. Our servers are protected by network firewalls, intrusion detection systems, and DDoS protection.
Access controls: Internal access to production systems follows the principle of least privilege. Every access is logged and audited.
Monitoring: Automated threat detection runs continuously. We monitor for unusual activity, unauthorized access attempts, and potential vulnerabilities around the clock.
Updates: We regularly scan for security vulnerabilities and apply patches promptly. Our development process includes security review at every stage.
Your Controls
We believe you should always be in control of your data and your access.
Revoke anytime: You can disconnect any registrar from Domain Pilot at any time. When you revoke access, we delete your stored credentials for that registrar immediately.
Export your data: You can export all your domain data at any time, in full, with no restrictions. Your data is yours.
Team permissions: If you're on a team plan, role-based access controls let you define exactly what each team member can see and do. Not everyone needs access to everything.
Two-factor authentication: Add an extra layer of protection to your account with MFA. We strongly recommend enabling this for all accounts, especially those managing business-critical domains.
What We Access and Why
When you connect a registrar, Domain Pilot uses your API key to:
- Read your domain list, registration dates, expiration dates, and auto-renew status
- Read DNS records for connected domains
- Read domain status and configuration settings
- Write DNS record changes (only when you explicitly make edits)
We never initiate domain transfers, purchases, or deletions through your registrar API. Domain Pilot is a monitoring and management layer. Your registrar remains the source of truth for all billing and ownership.
What We Don't Do
- We don't sell your data. Ever.
- We don't share your registrar credentials with third parties.
- We don't store your credentials in plain text, anywhere, at any point.
- We don't access your registrar accounts outside of the operations you initiate.
- We don't process domain payments or handle billing on your registrar's behalf.
Incident Response
In the unlikely event of a security incident, we commit to:
- Notifying affected users within 72 hours of confirmed breach discovery
- Providing clear details about what was affected and what actions you should take
- Working with security professionals to investigate and resolve the issue
- Publishing a transparent post-incident report
We maintain a documented incident response plan and conduct regular drills to ensure our team can respond quickly and effectively.
Responsible Disclosure
If you discover a security vulnerability in Domain Pilot, we want to hear from you. Please contact us at security@domainpilot.io with details of the vulnerability. We ask that you give us reasonable time to investigate and fix the issue before disclosing it publicly.
We appreciate the security research community and are committed to working with researchers who help us keep Domain Pilot safe for everyone.
Questions?
Security isn't a feature we ship and forget. It's built into every decision we make, from how we store your credentials to how we design new features. If you have questions about how we handle your data, reach out to us at security@domainpilot.io.
Your domains are critical to your business. The tools that manage them should be held to the highest standard.