Regulatory Site Blocking
Government blocking directives (NTC, CICC, PNP-ACG) from receipt to verified enforcement on the MikroTik routers. Nothing is blocked before a compliance administrator approves it.
Total directives
–
Active blocks
–
Pending tickets
–
Waiting verification
–
Waiting approval
–
Successful deployments
–
Failed (7 days)
–
Expired / revoked
–
Routers compliant
–
Last verified sync
–
Compliance workflow
- 1.Directive received
- 2.Document verification
- 3.Legal / scope check
- 4.Authorized approval
- 5.Policy generated
- 6.MikroTik deployment
- 7.Enforcement verified
- 8.Compliance report
Needs attention
Router compliance
Recent activity
Tickets are entered by hand or imported from the agency's list. Emails and links are never opened or acted on automatically. No official ticket API is connected.
Current policy
–
The scheduler also checks every router, repairs drift and retries failed or offline routers automatically.
How a router is blocked
- Domains: router DNS answers "does not exist" (or the sinkhole address). Works for subscribers who use the router as DNS.
- IP addresses: address list
onekonek-reg-blockand one filter rule at the top of the forward chain. - TLS host (optional): best effort for HTTPS; does not work with encrypted client hello / QUIC.
- Only items with the comment
ONE-KONEK REG [...]are ever changed. NAT, PPPoE, RADIUS, routing and other firewall rules are left alone. A configuration backup is taken before each change.
Deployment history
Reports state only what the system recorded: approvals, deployments, verification results and failures. URL targets are reported as enforced on the whole domain.
This log can only grow. Each entry carries the fingerprint of the entry before it, so a changed or deleted entry is detected.
Issuing agencies
Only directives from an agency marked authorized can be verified. Only a Super Administrator can change this list.