by ironcreed 0 (0 reviews)

IRONCREED Request Log

Name: IRONCREED Request Log
Author: ironcreed

Inspect bounded WordPress requests and optionally scheduled Hosting Ukraine nginx access logs with privacy controls.

IRONCREED Request Log ranks #47,616 among WordPress.org plugins with 0+ active installations, is #4,227 of 4,566 in the Security category, and was last updated Sep 22, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.1

v1.0.0 Current Version v1.0.0

Updated 17 hours ago Last Update on 22 Sep, 2026

Refreshed 13 hours ago Last Refreshed on

#4,227 of 4,566 in Security Actively maintained

View on WordPress.org

Rank

#47,616

— No change

Active Installs

— No change

KW Avg Position

N/A

— No change

Downloads

+36 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 50%

0+ 10+

15,949

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 5 more installs to reach 10+

Rank Changes

Current #47,616

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.0
Last Updated: Sep 22, 2026
Requires WP: 6.5+
Tested Up To: 7.1.1
PHP Version: N/A
Author: ironcreed

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

debugging privacy request log security

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,758

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Akismet Anti-spam: Spam Protection

5M+ installs

Wordfence Security - Firewall, Malware Scan, and Login Security

5M+ installs

#11

Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)

Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention

View all Security-and-spam-protection plugins

Frequently Asked Questions

Common questions about IRONCREED Request Log

No. It records requests only after WordPress loads.

It does not open arbitrary server files or present one source as complete. It records only requests WordPress actually sees and can optionally retrieve the hosting provider's current-day nginx archive through a read-only API. The two sources remain separate, with explicit visibility and privacy boundaries.

No. The provider adapter downloads the current day's nginx log and remains read-only with respect to hosting configuration.

On an explicit domain lookup, connection test or log fetch, and periodically after separate opt-in. Installing, activating, opening a screen or saving a manual connection does not contact the provider. A token entered for a test is used but not saved.

WP-Cron needs site traffic or an operator-configured system scheduler. Low traffic, disabled cron or failed loopbacks can delay execution. The UI shows the last and next attempt. Errors back off; Retry-After is honored for rate-limited imports. Each download covers today's archive only.

For a shared hosting virtual host, start with the main network site domain. Separately hosted mapped domains may need different IDs. IDs from the user header, hosting account or WordPress blog are different objects. Connections remain local to the configured site.

The plugin does not register an exporter or eraser because records have no reliable WordPress-user identity and an email-keyed lookup cannot correctly identify all related URI, IP, User-Agent, or Referer values. Administrators can filter and clear records by source, and uninstall removes all plugin data.