Behavior over single requests
Nexus looks for repetition, target and application context instead of turning one odd URL into a permanent verdict.
Behavior-aware runtime defence
Traffic is not identity. Context matters.
Traffic Shield evaluates repeated behavior, protected surfaces and site context so Nexus can respond to pressure without treating every unusual request—or every shared IP—as the same attacker.
Very Light / NormalUnder AttackShared-network awareExplainable actions
TRAFFIC SHIELDMONITORING
Pressure risingRepeated dynamic activity under watch
Shared networkClients kept distinct where evidence supports it
Verified crawlerAllowed with informational context
IP is evidence—not identity
Shared mobile networks, NAT and CGNAT are handled conservatively so one public address does not automatically become one attacker.
Temporary, readable response
Pressure states are designed to tighten protection when needed and relax again when the evidence window ends.
Context changes the verdict
A busy store, a crawler and an attacker can look similar for a few requests.
Traffic Shield works inside WordPress where Nexus can understand the surface being touched, the surrounding behavior and whether the activity is consistent with a real visitor, useful automation or sustained pressure.
- Very Light and Normal profiles for everyday operation
- Under Attack and Custom profiles for actively licensed PRO sites
- Shared-network-aware client continuity
- Bot, scanner and repeated-offender context
- Temporary pressure modes instead of permanent panic
Capability map
Runtime defence that understands more than the source address.
The goal is not to collect the most blocks. It is to make safer decisions under real WordPress traffic.
Protection profiles
Choose a practical baseline for ordinary operation, or temporarily tighten the runtime layer when a site is genuinely under pressure.
- Very Light
- Normal recommended
- Under Attack with active licence
- Custom with active licence
Repeated-offender context
Build local history when a source repeatedly touches sensitive or exploit-shaped surfaces instead of overreacting to one request.
- Short-window pressure
- Temporary escalation
- Reviewable evidence
Shared-network intelligence
Use privacy-preserving client continuity alongside the public IP so multiple real visitors behind one network are not automatically collapsed into one identity.
- CGNAT-aware design
- Stable-client context
- Cookie churn discounted
IP Control Center
Investigate, trust, watch, block and release individual sources from one operational view.
- Explicit manual controls
- Clear expiry
- Reason attached
Operational flow
Build confidence gradually, then relax when pressure ends.
Traffic Shield is designed to be proportionate rather than permanently suspicious.
Observe
Normal and unusual activity are evaluated in the context of the surface being used.
Corroborate
Repetition, automation and source/client evidence increase or reduce confidence.
Contain
Temporary protection is applied to the relevant source or surface when evidence becomes strong enough.
Relax
Temporary state expires or returns to normal when the pressure window clears.
Use context to protect without punishing ordinary traffic.
- Keep shared-network users distinguishable where evidence allows
- Separate verified crawlers from spoofed bots
- Prefer temporary and explainable action
- Keep normal logged-in and customer flows in view
Turn one weak signal into a site-wide punishment.
- Treat every bot as malware
- Assume one IP equals one actor
- Blindly block broad provider ranges
- 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 traffic before normal WordPress loading. Traffic Shield works during runtime where richer site and application context is available.
What profile should most sites use?
Normal Protection is the recommended everyday profile. Very Light is more relaxed. Under Attack and Custom are advanced profiles available while the Nexus PRO licence is active.
What happens on shared mobile networks?
Nexus does not treat the public IP as a complete identity. Where possible it combines network pressure with privacy-preserving client continuity and other evidence before escalating.
Are automatic blocks permanent?
No. Pressure responses are designed to be temporary and reason-bound. Manual controls remain explicit.
Lumiverse Nexus PRO
Traffic should tell a story before it triggers a punishment.
Traffic Shield is part of the Nexus PRO defense stack; advanced Under Attack and Custom profiles require an active licence.