Network-level blocking
Ads, trackers, malware, and phishing domains are stopped before a connection is made. Domain and suffix blocking only — no content inspection.
NEAR ADGUARD blocks ads and trackers at the DNS layer for iPhone, iPad, and Mac. No app. No VPN. Just an encrypted DNS-over-HTTPS profile and a resolver that never stores allowed query names.
Free DoH endpoint
No account required
https://dns.nearguard.biz.id/dns-queryWhat it does
NEAR ADGUARD resolves allowed domains through Cloudflare with a Google fallback, and returns NXDOMAIN for blocked domains. It never inspects page content and never stores allowed query names.
Ads, trackers, malware, and phishing domains are stopped before a connection is made. Domain and suffix blocking only — no content inspection.
Install a signed-by-you DNS profile in Safari. Works with iPhone, iPad, and Mac through the native DNS settings. Android is not supported.
Every request is encrypted HTTPS on port 443. No plaintext port 53, no DoT, no DoQ, and no traffic interception.
Allowed query names are never stored. Free clients get aggregate counters only. Registered users choose whether blocked domains are logged.
A registered account gets a personal DoH URL, optional per-device labels, and a dashboard with blocked-domain and rate-limit visibility.
Free infrastructure has real limits. The service documents them, applies request-rate limits, and uses a circuit breaker to stay inside the monthly cap.
Free
Use the public endpoint at /dns-query. You get the same blocklist, encrypted transport, and NXDOMAIN responses. Free traffic is rate-limited per IP and receives aggregate counters only.
Registered
A registered account gets a personal DoH URL at /{username}, optional device labels, and a dashboard. Blocked-domain logging is opt-in and can be deleted at any time.
How it works
Your device sends an encrypted DNS query to Vercel. The resolver checks an in-memory blocklist, applies rate limits, forwards allowed queries upstream, and returns a DNS response. Event counters are flushed after the response, never before it.
01
Open the profile in Safari, allow the download, then install it in Settings. The profile points your device at the DoH endpoint.
02
Known ad, tracker, malware, and phishing domains return NXDOMAIN with a short TTL. Everything else is forwarded to Cloudflare, with Google as fallback.
03
Registered users can see blocked-domain aggregates and recent events. Free clients only produce aggregate counters.
iPhone / iPad / Mac
The profile is unsigned. iOS will show an “Unsigned” warning; that is expected. Review the profile before installing and remove it at any time in Settings.
Privacy
Allowed query names are never stored. Free clients get aggregate counters only. Registered users can opt into blocked-domain history and delete it at any time. Real IP addresses are encrypted at rest and visible to administrators only after PIN verification, with an audit log.
Read the privacy policyAES-256-GCM ciphertext, separate table, no client-readable policies.
Decoy IPs by default. Real IPs only after a short-lived, audited reveal session.
The hot path records counters, not the names of allowed domains.
Blocked events, daily aggregates, idle devices, and encrypted IPs are purged on schedule.
FAQ
No. On iOS, iPadOS, and macOS you install a DNS configuration profile. The system sends DNS queries to NEAR ADGUARD over HTTPS. No VPN tunnel is created and no app is required.
No. Android is out of scope. The service is designed around Apple's DNS profile format and iOS/macOS behavior.
No. A /username path is an identifier, not a secret. Anyone who knows it could send queries through it and affect that account's stats and quota. Per-IP limits, anomaly flags, and optional device labels reduce abuse. Do not treat the username as a password.
Free clients produce aggregate counters only: requests, blocked, rate-limited, country, and last-seen. Free clients do not get per-domain logs.
A circuit breaker throttles free-tier traffic first, then hard-throttles free traffic, then registered traffic, and finally all DoH traffic except administrators. The goal is to keep the deployment inside the Vercel Hobby invocation cap instead of being paused.
No. This deployment is personal and non-commercial on Vercel Hobby. Commercial use requires a different Vercel plan and a fresh review of limits and terms.
The resolver runs as a Vercel Function. Each DoH query is one invocation. At the documented starting scale of four devices at 4,000 queries/day, the service stays within the Hobby invocation and CPU allowances with headroom.
Use the free endpoint or create an account for a personal path and a dashboard. Either way, allowed query names stay out of the logs.
NEAR ADGUARD is a personal, non-commercial project. Every DNS query is a serverless request. Free infrastructure has hard limits, and the circuit breaker protects the deployment before those limits are reached.