Setting Up WordPress Security in Minutes: The ReportedIP Hive Quickstart
WordPress security setup usually means juggling three plugins and a dozen settings screens. Since version 2.1.54, ReportedIP Hive replaces that with a single quickstart page that ships privacy-first defaults, so a fresh site is protected before you finish your coffee.
This guide walks through what the quickstart configures, what the dashboard shows afterwards, and how to tune it without breaking real visitors.
What is ReportedIP Hive?
ReportedIP Hive is a complete WordPress security plugin: 18 attack sensors, four 2FA methods, progressive IP blocking and an opt-in community threat network in one drop-in. The plugin is free and GPL-2.0; paid plans only add server-side comfort like managed mail/SMS relay. The full ReportedIP Hive feature set is documented on the product hub.
What the quickstart configures
The quickstart asks two questions instead of walking through ten steps. First, a mode: Community Network, which pulls in reputation data from thousands of sites and needs a free Community Access Key, or Local Shield, which makes zero outbound calls and relies on local detection only. Second, for Community Network, that key, checked live against the account so the page can read the site’s plan and apply the matching recommendation automatically.
Everything the recommendation switches on is listed on the page itself, brute-force protection, the firewall, community reputation blocking from 75% confidence, bot verification and 30 days of logs on every plan, plus Tor blocking, HSTS and 90-day logs on Professional and a one-year audit trail on Business. Three settings stay as visible toggles rather than being preconfigured, because they change what visitors or administrators actually see or receive:
- 2FA for administrators. On by default with a 7-day grace period; codes arrive by app, e-mail, passkey or SMS, and the admin’s own enrolment starts right after activation.
- “Protected by ReportedIP” footer badge. Shows visitors the site is protected and helps the community network grow.
- Alert mails. Sent to the site’s admin address on critical events.
An “I will set everything up myself” link applies the same plan-aware recommendation as a baseline but opens the full settings screen instead of the dashboard, for anyone who wants to review every value before going live. A site with an existing settings export can skip the questions entirely and import it from the same page.
What changed from the old wizard
Version 2.1.54 removed the previous ten-step wizard (Welcome, Connect, Protection, 2FA, Privacy, Notifications, Login, Promote, Done) in favour of the single page described above. A bookmarked or documented link to the old wizard URL redirects straight to the quickstart, so nothing that pointed at the setup flow before this update breaks.
What the dashboard shows now
After setup, the dashboard renders 7- and 30-day Chart.js trend lines for blocked IPs, attacks, sign-ins and spam, with an activity list showing the five latest events. Five list-table screens back it up: Blocked IPs, Whitelist, Security Logs, API Queue and the 2FA admin grid, each searchable, sortable and bulk-actionable. API call statistics and the licensed-domains count now live on the Community page instead, next to the quota they already shared, and Community Network installs see the three latest posts from reportedip.de’s news feed at the bottom, in the admin’s own language.
Security Logs are severity-filterable and export to JSON or CSV. The Blocked IPs screen lets you unblock, move an IP to the whitelist, or export the list; the Whitelist screen accepts a CSV import for trusted ranges.
Tune it without blocking real users
Enable Report-Only mode under Settings → Blocking before you flip enforcement on. Every event is logged exactly as it would have been blocked, but no IP is ever rejected, ideal for tuning thresholds against live traffic. When the numbers look right, turn enforcement on and the same thresholds start blocking.
Related guides
- Form execution proof and the new quickstart in full
- The 18 attack sensors and their default thresholds
- Four two-factor methods built into the core
- GDPR-first WordPress security and privacy defaults
See the WordPress plugin documentation for the full settings reference, or browse the rest of the ReportedIP Hive plugin guides. The plugin is public and auditable on GitHub.