Repository navigation
DNS Check Scheduling
TL;DR: verified domains get re-checked automatically every 6+ hours; a newly-verified domain gets its first check within one tick, not a full wait.
A background sweep (run_dns_check_sweep, every 15 minutes) re-checks every
verified domain whose last check is missing or older than 6 hours — not
tighter than that on purpose: several checks (STARTTLS in particular) open a
real SMTP connection to the domain's own mail servers, and DNS records don't
change often enough to justify repeating that every few minutes. A
newly-verified domain still gets its first check within one tick rather than
waiting the full 6 hours, since it has no prior check to compare against.
Unverified domains are never checked automatically — DNS ownership has
to be proven first (a TXT challenge at _yadt-verify.<domain>)
so an organization can't see check results for a domain they don't control.
See Onboarding Your First Organization
step 5 for the verification flow, and
DNS Verification Issues if it's stuck.
← Back to the README · Live demo · Report an issue · MIT licensed
- Quick Start: Docker Compose
- Deploying with Portainer
- Deploying on Azure
- Configuration Reference
- Onboarding an Organization
- IMAP Mailbox
- Google Workspace Mailbox
- Sign-in Providers
- Multi-Tenancy & RLS
- DMARC Subdomain Inheritance
- Report Attribution
- SPF Conditional Mode
- Detected Domains
- DNS Check Scheduling
- Domain Rating
🏗️ Architecture
🗺️ Roadmap