Dynamic pressure
Track repeated sources, endpoints, methods and user-agent spread over meaningful time windows.
Behavior-aware runtime defence
See pressure patterns—not just individual requests.
Traffic Shield observes bots, repeated sources, dynamic endpoints, network clusters and site-specific behavior so abusive pressure can be contained with context.
Bot classificationRepeat offendersPressure modesIP Control Center
TRAFFIC SHIELDMONITORING
Repeated scannerSource entered under-watch state
Network clusterMulti-IP pressure observed
Verified crawlerAllowed with informational context
Network context
Recognize multi-IP pressure without blindly blocking whole providers or arbitrary ranges.
Readable verdicts
Show allowed, under-watch, suspicious and blocked activity with the reason attached.
Context changes the verdict
A product page, login form and static asset do not face the same traffic.
Traffic Shield works inside the normal WordPress flow, where logged-in state, WooCommerce actions, verified crawlers and site-specific behavior can inform a safer decision.
- Bot and scanner classification
- Repeated-offender scoring and temporary blocks
- IP investigation, trusted addresses and emergency control
- Adaptive login, WooCommerce and network pressure states
Capability map
Runtime protection for requests that need context.
The layer watches behavior across requests rather than assigning every visitor a permanent label after one unusual URL.
Bots and scanners
Detect known abusive crawlers, scanner-style paths and noisy automation while preserving useful bot traffic.
- User-agent and request patterns
- Verified crawler safeguards
- Category-specific actions
Repeated offenders
Build local history for sources that repeatedly hit sensitive routes or exploit-style endpoints.
- Short-window pressure
- Temporary escalation
- Reviewable source timeline
Range pressure watch
Observe repeated multi-IP activity within a specific IPv4 /24 before considering a conservative temporary response.
- Unique source counts
- URL and user-agent spread
- Auto-block optional
IP Control Center
Investigate, trust, watch, block and release IPs from one operational view.
- Emergency controls
- Threat Network context
- Clear expiry and reason
Operational flow
From normal traffic to temporary containment.
Traffic Shield builds confidence gradually and relaxes when the pressure window ends.
Baseline
Normal site traffic establishes current behavior and protected routes.
Accumulate
Repeated hits, targets and automation patterns add context.
Escalate
A pressure state tightens the relevant protection without globally locking the site.
Relax
Temporary controls expire or return to normal after the quiet window.
Use behavior to make local decisions.
- Separate verified crawlers from spoofed bots
- Prefer temporary and explainable actions
- Respect trusted IPs and normal logged-in workflows
- Keep range blocking conservative and specific
Punish the whole internet for one noisy request.
- Blindly block broad ASN ranges
- Treat every bot as malware
- Add abuse score solely for verified commerce crawling
- Keep temporary pressure controls forever
Feature questions
What buyers usually want to know.
Is Traffic Shield the same as Early WAF?
No. Early WAF handles high-confidence requests before normal WordPress loading. Traffic Shield works during runtime where richer site context is available.
Can it block a whole /24 range?
Only when the optional range auto-block is enabled and a specific /24 crosses high-confidence multi-source pressure thresholds. Watching and reporting can remain enabled without automatic range blocking.
Will verified Googlebot be punished for a crawlable add-to-cart URL?
No. Verified crawlers are not classified as suspicious solely for following crawlable commerce-action, wishlist, filter or ordering URLs.
Are blocks permanent?
Automated pressure responses are designed to be temporary and reason-bound. Manual controls remain explicit.
Lumiverse Nexus PRO
Turn traffic into a security story you can inspect.
Traffic Shield, pressure modes and IP controls are core Nexus PRO modules.