Malware, phishing, and scam blocks
Start with a small risk baseline across your devices before adding stricter filters.
Personal DNS filtering for home, travel, and testing
Personal DNS filtering should cover the laptop, phone, tablet, home office, travel device, and test hardware that make DNS requests every day. Veilty helps you block risky domains, reduce ads and trackers, proxy selected travel sites, and keep useful history protected.
Metrics
Preview demo DNS metrics for a protected family or team network.
Personal DNS controls for home and travel
Start with risk blocks, travel contexts, E2EE history, narrow rules, and optional proxy for IP-location age or geo prompts while abroad.
Tracker and ad reduction
Reduce tracker and ad domains for your laptop, phone, tablet, home office, and travel setup.
Profiles for your device contexts
Use profiles where they help. If one profile works, do not create five.
E2EE personal history
Use protected stored history to answer why a site stopped loading or a resolver drifted without making retained DNS history plain server-readable.
Travel proxy for selected sites
Route selected web domains through a proxy when travel puts your visible IP somewhere a site requires age registration or blocks content by region.
Rules you can still explain
Use narrow allow, block, or proxy rules when lists are too broad, and keep notes so future you knows why each rule exists.
The first personal setup should stay understandable
Personal DNS control works best when the baseline, device contexts, and history settings are easy to review.
When personal DNS filtering is the right layer
Use this checklist before choosing a tool: DNS helps with domain-level blocks, selected redirects, device contexts, and protected stored activity history for recent questions.
Good DNS-fit problems
Choose Veilty when the decision belongs at the DNS layer: domains, device settings, category blocks, redirects, and recent domain-level evidence.
DNS is a good fit when you want to block malware, phishing, scams, suspicious domains, and a few personal manual blocks without turning DNS into a complicated rule project.
A DNS tool helps when your daily laptop, travel phone, home-office machine, and test device should not all share the same settings because they use different networks or tools.
A DNS tool helps when you want recent context for blocks, redirects, suspicious lookups, or resolver drift. E2EE protected stored activity history uses user-held keys, while live DNS requests still pass through resolver processing.
Get early access for personal DNS filtering
Join if you want simple DNS filtering with E2EE protected stored activity history, clear device contexts, narrow rules, and proxy for selected travel sites.
100 Founders
First 100 verified members. All self-serve features, including proxying when available.
1,000 Families
Next 1,000 verified members. All family features except traffic proxying.
Live waitlist
Loading real waitlist data.
Top referrals
Loading leaderboard.
Email-only signup. Duplicate, self-referral, temporary, or spam signups may be removed before invites go out. Early access does not change the Waitlist Terms or Privacy Policy.
Related personal DNS guides
Use these guides to compare privacy, VPNs, blocklists, and home resolver tradeoffs.
Personal DNS filtering FAQ
Plain answers for people who want more control over their own resolver setup, device setup, and activity history.
DNS filtering controls whether domain lookups should resolve, block, or use a proxy route. A VPN changes broader network routing and can protect traffic on untrusted networks. They work well as separate layers.
No. Encrypted DNS protects traffic on the path to the resolver. The resolver still processes the request. Privacy also depends on what the resolver stores and who can read stored history.
It can show domain-level activity such as domains, timing, device or profile labels, and what was allowed, blocked, or redirected. For page content, messages, videos, searches, and app behavior, use the controls inside those apps and platforms.
Veilty protects stored DNS activity history with E2EE and user-held keys when you enable visibility. Live DNS requests still pass through resolver processing, but you should not treat retained personal history as a plain server-readable browsing log.
Keep enough to troubleshoot recent problems and tune your setup. When raw detail stops helping, prefer shorter retention or aggregated views.
Only if the devices need different rules. A daily laptop and travel phone may need different settings. Two devices used the same way may not.
Use rules when lists are too broad, and keep them narrow enough to remember. Allow one banking, login, update, or work domain for a clear reason instead of loosening the whole setup.
No DNS filter can see everything inside an app. DNS can reduce known tracker domains, but app settings, browser controls, permissions, and operating-system privacy settings still matter.
Redirects can proxy selected web domains so an IP-based region check sees the proxy route instead of the device IP. This can help when travel changes content availability or adds age-registration prompts, but account region, ID, payment details, GPS, app-store region, device checks, service terms, and local rules may still apply.