Managed protection for family devices
Start with maintained malware, phishing, scam, adult-content, ad, and tracker lists instead of maintaining every domain yourself.
Family DNS filtering for kids, households, and parents
Give each household device protection that fits how it is used. Veilty combines baseline and enforced Space policies with assigned filters and rules, blocks risky domains, keeps exceptions narrow, and encrypts retained activity.
Metrics
Example DNS activity summary for a protected family or team network.
Family DNS controls for household devices
Block obvious risks with baseline and enforced Space policies, assign filters or rules only where device needs differ, and keep exceptions narrow.
Filters and rules by device need
Assign different filter or rule sets when a child's tablet, teen phone, family TV, school device, guest device, or parent laptop needs different protection.
Private family activity history
User-held keys protect retained DNS activity and summaries, so family history stays useful without becoming readable to Veilty.
A Space for the household
Group household devices, trusted adults, and reusable baseline and enforced policies in one family Space.
Transparent proxying
Send a chosen site through a Veilty exit in another country when it responds differently to the visible IP location.
Narrow household exceptions
Allow or block one domain for one child, teen, shared screen, or school device instead of weakening the whole setup.
The first family setup should stay simple
Start with the smallest useful baseline policy, test it on real devices, and explain how someone can ask for a narrow exception.
When family DNS filtering is the right layer
DNS is useful for domain-level safety, baseline and enforced Space policies, assigned filters and rules, and recent block context. It cannot supervise everything inside an app.
Good DNS-fit problems
Choose Veilty for baseline and enforced Space policies, assigned filters and rules, transparent proxying, and recent activity details.
DNS is a good fit when the first job is domain-level protection: adult content, malware, phishing, scams, and a short list of sites the household wants blocked.
Assign separate filter or rule sets when a child's tablet, teen phone, shared TV, guest device, and parent laptop should not all inherit one blunt household setup.
Recent activity can explain which device, site, and rule produced a block. Saved details and summaries remain encrypted until a member with access to that family Space opens them.
Get early access for family DNS filtering
Join the wait list for device-based family DNS filtering, narrow exceptions, transparent proxying, and private activity history.
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.
Related family guides
Start with device setup, then compare DNS privacy, encrypted DNS, and parental-control tradeoffs.
Family DNS filtering FAQ
Plain answers for parents setting up DNS filtering, Space policies, device rules, logs, and bypass paths at home.
Family DNS filtering checks the site names requested by household devices and allows or blocks them according to the rules you choose.
DNS filtering handles domain-level protection. Device controls still handle app installs, screen time, purchases, account settings, and supervision inside apps.
Sometimes. Mobile data, VPNs, private browsing relays, manual DNS changes, and browser settings can use a different route. Device controls help prevent unwanted changes.
Yes. Families can reduce known ad and tracker domains on shared screens, tablets, and guest devices, while keeping lighter rules for parent or school devices when breakage matters.
A member with access to the family Space can see the device, site name, time, action, and rule behind its saved activity record. It does not show every page, message, search, or video inside an app.
Family history belongs to its Space. A member can open encrypted activity details and summaries only when their assigned role gives them access to that Space.
Space roles decide who can access the family Space, manage its people and devices, choose shared protections, and review the retained history available there.
Make the smallest safe change. Allow or block one domain for one device or Space, record the reason, and revisit the exception when the device or service changes.
A chosen site can use a Veilty connection from another location instead of your real IP. This does not change the location of your whole device, and the site may still use your account, cookies, payment details, or device settings to identify your region.