A device asks for a domain
Your phone, laptop, or other configured device sends the domain lookup to Veilty. Veilty must process this live request to decide what answer to return.
Secure DNS Filtering for Families, Teams, and Personal Devices
Veilty applies DNS rules to each device, blocks risky domains, and explains each decision without exposing retained activity to Veilty. Families and teams can share control in Spaces, while transparent proxying changes only a chosen site's route.
Metrics
Example DNS activity summary for a protected family or team network.
A DNS request, from lookup to private history
Veilty handles the live lookup, applies the right rules, returns one clear outcome, and encrypts only the activity you choose to keep.
DNS control that stays understandable
Apply protection by device, keep retained activity end-to-end encrypted, share responsibility in Spaces, and use transparent proxying where it helps.
End-to-end encrypted activity history
Retained DNS activity is end-to-end encrypted and belongs to a Space. Members open details and summaries only for Spaces their assigned roles let them access, using user-held keys on their own devices.
Transparent proxying
Route a chosen site through a country-specific Veilty connection. Other sites and apps keep their normal route.
Spaces for shared control
A Space groups devices, responsible people, and reusable baseline and enforced policies for one household, team, client, or lab.
Managed threat protection
Start with maintained malware, phishing, and scam lists instead of researching and maintaining every risky domain yourself.
Ad and tracker reduction
Reduce connections to known ad and tracker domains, then adjust the strength for devices that need different compatibility.
Custom rules
Override a managed list for one domain with an explicit allow, block, or transparent proxy rule.
Choose the setup that fits your devices
Use baseline and enforced policies for shared Space protection, then assign filter or rule sets when a particular device needs different behavior.
For families
Give each household device suitable protection without forcing one blunt setup on everyone.
A child's tablet, teen phone, shared TV, school laptop, guest device, and parent phone should not inherit one blunt DNS setup.
Group household devices in a Space, apply baseline and enforced policies, and add device-specific filters or rules only where needed.
For teams
Keep risky domains blocked, preserve enforced Tenant policies, and give different work devices suitable filters and rules.
A finance laptop, contractor device, shared kiosk, and lab system need different DNS behavior, while team members need different management access.
Create a Tenant for each team, client, or lab, apply baseline and enforced policies, then assign filters and rules where device needs differ.
For personal use
Protect personal devices and troubleshoot blocks without making retained DNS history readable to Veilty.
A laptop, phone, travel setup, and test device can drift across networks, VPNs, browser DNS, and one-off rules.
Use private records and summaries to find the cause, then add one narrow rule or transparently proxy the affected site.
Use DNS where DNS can help.
Before choosing a layer, ask whether the problem starts with a domain. Veilty can allow it, block it, or transparently proxy that chosen site through Veilty.
Choose Veilty when the problem starts with a domain
Use Veilty when the decision starts with a domain: allow it, block it, send that site through Veilty, or review private context before changing a rule.
Block malware, phishing, scam, adult, tracker, ad, or chosen domains before a site or app connects to them.
Redirect that site through Veilty so it sees Veilty's connection. Every other site keeps its normal route.
Assign device-specific filter or rule sets to the child's tablet, finance laptop, shared TV, guest device, or test machine instead of forcing one setup across the whole network.
Use an enforced Space policy for rules that local device settings must not weaken.
Use a private activity record to see which device requested the domain, which rule matched, and what Veilty did.
Allow, block, or redirect one login, update, banking, or streaming domain without relaxing the whole setup.
Get early access to Veilty
Your signup encourages Veilty development because early access requests are the only demand signal we track. Verified requests can qualify for the first account batches.
100 Founders
The first 100 verified early access requests qualify for Founder access.
1,000 Families
The next 1,000 verified early access requests qualify for Family plan launch priority.
Wait list
Loading wait list details.
Top referrals
Loading referral ranking.
Email-only wait-list signups. Duplicate, self-referral, temporary, or spam entries may be removed from the wait list. Wait-list signups and account invitations are covered by the Wait List Terms and Privacy Policy.
What we are making ready
Public release and post-release plans
DNS filtering FAQ
Plain answers about device-aware DNS filtering, protected activity history, VPNs, privacy settings, and everyday setup.
Veilty is a DNS filtering service for families, teams, and personal devices. It applies rules by device, blocks risky domains, organizes shared control in Spaces, protects retained activity with end-to-end encryption, and supports transparent proxying.
Encrypted DNS activity records and summaries belong to a Space. A member can open history only for Spaces their assigned roles let them access. Account membership alone does not grant access to every Space or its retained activity.
Yes. Like any DNS service, Veilty has to handle a live domain request to allow it, block it, or transparently proxy a chosen site through Veilty. Encryption protects the activity record and summary stored afterward.
Activity records can show which device requested a domain, what Veilty did, and which rule matched. Private summaries help you spot broader patterns without reading every individual record.
No. A chosen site routed through Veilty sees Veilty's connection instead of your real IP, but other sites and apps keep their normal route. This does not change the country or identity of your whole device.
No. Transparent proxying applies only to chosen sites; it does not route every app or connection on the device. It is not a whole-device country switch or anonymity service, and a site can still use account, cookie, payment, GPS, or device information.
Invitations add people to the Veilty account. After they accept, assign roles to give them access to a Space. An invitation does not grant Space access by itself. The owner controls ownership and admin access. Admins manage people, devices, and shared protection choices. Members manage devices and see the shared setup. Viewers can read without changing it.
Baseline and enforced policies are reusable across Spaces. Within a Space, resources added there may override its baseline policy. An enforced policy takes precedence and cannot be weakened by those resources.
Veilty can block known malware, phishing, scam, unwanted, ad, and tracker domains. DNS filtering works at the domain level, so it cannot judge every page, message, video, search, or action inside an app.
Start with trusted filter lists, then add a narrow rule when one domain needs a different outcome. Baseline and enforced policies shape shared Space protection, while filter and rule sets assigned to a device handle device-specific needs.