MERAVIOXPRIVATE CONTROL PLANE
Welcome back.
Sign in to your Meraviox workspace. Your existing administrator credentials stay the same.
Sign in to your Meraviox workspace. Your existing administrator credentials stay the same.
Actual filtering-boundary counters across Standard DNS, DoH and DoT. Diagnostic requests are included.
Active validated list rules
These are the existing Meraviox counters. Native AdGuard statistics may remain disabled; past traffic is never invented.
Checking service controls
An address is not a person or an account. NAT, VPNs, IPv6 rotation and UDP spoofing affect attribution. First/last observed are measurements, not registration dates.
| abuseConfidenceScore | DNS ACCESS | CONTROL |
|---|
AbuseIPDB scores use a 30-day report window and a 24-hour cache. Scores ≥70 are High risk, not proof of abuse. Automatic bans require sustained local gateway abuse; reputation alone never bans. Exact source IPs are sent privately to AbuseIPDB; no queried domains or automatic abuse reports are sent. UDP-only observations are not looked up because their source can be spoofed. Country flags represent approximate GeoIP network location, not nationality. Collection gaps are not reconstructed. Banned addresses remain visible as observations. Restrictions apply only to their stated DNS scope; an observation does not prove a request was admitted.
Captured DNS requests attributed to this exact source IP. A shared address can represent multiple people or devices; DNS requests do not prove a page was visited.
Choose a Source IP from Observed clients.
No history loaded
| DOMAIN / TYPE | TRANSPORT | VERDICT | LATENCY | OBSERVED · MYT |
|---|
Only retained records with a verified source-IP association are included. Standard DNS/DoT gateway queries without per-query attribution are excluded. IP/country association expires after7days, even though domain-only records may remain for14days. Collection is sampled under load; this is not a complete browsing history. Pages share a fixed time cutoff; late imports and expiry can change available records. Refresh history includes new records. No missing history is reconstructed.
Actual AdGuard filtering decisions, including client traffic and internal diagnostic checks. DNS requests do not reveal full URLs or prove a page was visited.
Checking collector
| DOMAIN / TYPE | CLIENT / COUNTRY | VERDICT | LATENCY | OBSERVED · MYT | CONTROL |
|---|
IP and country are removed after 7 days; domain records expire after 14 days. Gateways without verified original-client attribution are explicitly labelled. Standard DNS and DoT currently share a backend gateway address; per-query client IPs are not inferred from timing. With client IP shows only attributable records; country flags are approximate. Ban opens a timed, confirmed form for the observed client IP. Unattributed gateway rows cannot identify a target to ban. A queried or filtered domain alone is not evidence of DDoS; review actual rate-limit events in Security & bans. Maximum 500,000 retained rows; under load, coverage may be incomplete.
Custom rules preserve the validated primary list. Changes use AdGuard's private API and do not restart DNS services.
Exact host by default. Operational canaries, public suffixes, private names and Meraviox service domains are protected.
HTTPS-only retrieval, normalization, full-engine canaries and last-known-good recovery remain enforced.
—Original source · SHA-256—Large changes remain held for review. This button runs the existing validated updater; it cannot force unsafe changes through. A successful check can leave the active snapshot unchanged.
Actual gateway limit violations. Filtered ads and ordinary NXDOMAIN responses do not trigger bans. IPs can be shared; countries are approximate.
No CIDR or permanent bans. Infrastructure, loopback and Cloudflare proxy networks are protected. DNS bans leave SSH, status websites and other applications accessible.
| SOURCE / COUNTRY | SCOPE / ACTOR | REASON | START · MYT | EXPIRY · MYT | CONTROL |
|---|
| TIME · MYT | IP / COUNTRY | PROTOCOL | REASON | COUNT | ACTION |
|---|
UDP sources are unverified and can be spoofed. Automatic UDP bans affect only UDP53 for60seconds. Sustained TCP/DoT or conservatively proven DoH abuse can trigger5minute bans. Global/subnet pressure and single bursts do not blame individual clients. Existing per-IP/subnet/global rate and connection limits remain active when automatic bans are paused.
Administrative actions are distinct from DNS request activity. Credentials and session tokens are never included.
| TIME · MYT | ACTOR | ACTION | DETAIL |
|---|