WordPress security / Open Source

Invalid Traffic Blocker

A published WordPress plugin connecting configurable traffic controls with IP intelligence.

MY ROLEPlugin author and maintainer
DELIVERY CONTEXTStandalone WordPress plugin; not the IVTB SaaS platform
TECHNOLOGYPHP · WordPress APIs · IPHub API · JavaScript
Invalid Traffic Blocker: authentic public website captured 13 November 2026

Public website · captured 13 November 2026. Figures shown within the interface belong to the source website.

01 / PROJECT NOTES

The integration problem

WordPress publishers need clear controls for handling suspicious traffic. Invalid Traffic Blocker connects IPHub intelligence to settings inside WordPress, so site owners can manage the integration from their existing dashboard.

02 / PROJECT NOTES

What I developed

I built the provider configuration, blocking controls, trusted-traffic settings and lookup handling, using WordPress settings APIs and sanitisation. The plugin is published in the official WordPress directory with public source available.

03 / PROJECT NOTES

A request-level workflow

Applicable settings and trusted-IP handling determine when a provider lookup is needed. The plugin interprets IPHub intelligence according to the selected configuration. The diagram below explains the workflow.

04 / PROJECT NOTES

Handling provider failures

Cache controls and a cooldown after API failure help manage the dependency on an external intelligence service. That boundary is part of the plugin’s operational design, alongside the site owner’s blocking policy.

05 / PROJECT NOTES

WordPress ownership and updates

A plugin shares an environment with themes and other extensions. Settings, lifecycle hooks and data handling need to respect that host application. The engineering work is therefore expressed through WordPress APIs rather than editing WordPress core.

06 / PROJECT NOTES

Published software

The plugin is available through the official WordPress directory, with source code open for inspection. It gives publishers configurable traffic controls within the application they already use.

Explore the boundaries.

A simplified view of the application. Select a component to explore its role.

Simplified architecture study · NOT A LIVE SYSTEM

The plugin runs within the host application and reads its configured controls.

Configuration, trusted traffic and cached information affect the lookup path.

IPHub is an external provider boundary; the plugin applies its configured response.

Project summary & sources.

  • Published in the official WordPress plugin directory.
  • Public source available for inspection.
  • Configurable provider integration and operational controls.

THE PUBLIC EXPERIENCE / TWO VIEWPORTS

One product.
Different contexts.

Desktop and mobile views of the public website.

Open desktop capture ↗Open mobile capture ↗
Invalid Traffic Blocker: authentic public website on a mobile viewport

A RELATED ENGINEERING CHALLENGE?

Let’s understand
what needs to work.

Discuss a similar project ↗