Login Security with Telegram Alerts vs Quantely Activity

Login Security with Telegram Alerts is your comprehensive solution for fortifying WordPress login security and staying informed about critical site activities. It actively combats brute-force attacks, enhances user authentication with multi-factor options, and provides real-time alerts directly to your Telegram. Scalable for any site size, from personal blogs to large enterprises, it ensures your WordPress site remains secure and you’re always in the loop. Key Features: Login Security with Telegram Alerts is packed with powerful features designed to give you peace of mind and full control over your site’s access. Brute-Force Protection: Automatically blocks suspicious IP addresses after a configurable number of failed login attempts, effectively preventing dictionary attacks and credential stuffing. Real-time Telegram Notifications: Receive instant alerts for failed login attempts and successful logins, delivered directly to your chosen Telegram channel, group, or private chat. This provides immediate awareness of critical site events, enabling prompt action. Cloudflare Turnstile (Anti-Bot): Protect your login form from bots and automated brute-force attacks using a privacy-friendly, invisible alternative to reCAPTCHA. New Device Login Alerts: Get instant email and Telegram notifications when a user logs in from an unrecognized device or browser. API Protection: Easily disable XML-RPC and restrict the WordPress REST API to logged-in users only, closing common vulnerabilities. Comprehensive Activity Logging: Maintains detailed records of both failed and successful login events, capturing critical information such as IP addresses, usernames, login times, and user agents. This log is invaluable for auditing and identifying suspicious patterns. IP Management: Block or unblock IP addresses directly from the Activity Log with one-click actions. Administrators can manually manage IP blacklists and whitelists from the plugin’s settings page. WordPress Core Files Integrity Check: Verify that WordPress core files haven’t been tampered with by comparing them against official checksums from WordPress.org. File Permissions Management: Automatically check and fix file permissions to match WordPress security standards, ensuring your installation follows best practices. Custom Admin URL: Hide your wp-admin login URL by creating a custom access point, adding an extra layer of security by obscurity. Geolocation Integration: Includes location data in Telegram notifications, adding crucial context to security alerts and aiding in the investigation of suspicious activities. Optional Email Two-Factor Authentication: Site administrators can enable an opt-in extra login step; users who choose to turn it on for their own account will be emailed a one-time verification code (delivered as a polished HTML email) each time they log in. User-Friendly Admin Interface: An intuitive, tabbed settings page contributes to a clean and easy-to-use experience. Why Choose Login Security with Telegram Alerts? Comprehensive Security: Provides advanced features that actively defend your site against common and persistent threats. Instant Awareness: Critical updates are delivered directly to Telegram, facilitating immediate action and providing peace of mind to site administrators. User-Friendly: Engineered for quick setup, often achievable in minutes, with an intuitive interface that makes configuration accessible to users of all technical levels. Performance Optimized: Built with efficiency in mind, ensuring that robust security measures do not compromise site speed. Dedicated Support: A passionate team is committed to providing prompt and helpful support, aiming to ensure users maximize the plugin’s potential. Compatibility & Requirements: WordPress Version: 5.0 or higher (Tested up to 7.1) PHP Version: 7.2 or higher (PHP 7.4+ recommended for optimal performance and security) Performance Considerations: Login Security with Telegram Alerts is designed with performance in mind: Efficient API Calls: When interacting with external services like Telegram’s API, the plugin uses WordPress’s built-in HTTP API for reliable and performant requests, minimizing impact on page load times. Optimized Database Interactions: Designed to minimize database queries and employs best practices for data storage and retrieval, ensuring your site’s database remains lean and responsive. Lightweight Codebase: Development emphasizes avoiding bloated scripts and unnecessary assets, ensuring the plugin adds minimal overhead to site resources. Security Best Practices: Beyond merely claiming to be “secure,” Login Security with Telegram Alerts implements rigorous security measures: Nonces: All critical actions and forms within the plugin utilize WordPress Nonces to protect against Cross-Site Request Forgery (CSRF) attacks. Input Sanitization: All user input is rigorously sanitized before processing or storage to prevent malicious code injection, such as Cross-Site Scripting (XSS) attacks. Output Escaping: Data displayed on both the frontend and backend is properly escaped to prevent XSS vulnerabilities. Capability Checks: Access to plugin functionalities is strictly controlled by checking user capabilities using current_user_can(), preventing unauthorized users from performing actions they are not permitted to. Regular Audits: The plugin’s codebase undergoes regular scanning and updates to address emerging security vulnerabilities. Internationalization (i18n): Login Security with Telegram Alerts is fully internationalized, allowing for seamless translation into any language. All strings are meticulously wrapped in gettext functions, and a dedicated text domain (login-security-with-telegram-alerts) ensures compatibility with WordPress’s robust translation system. Third-Party Services This plugin may connect to external services to provide certain features: Telegram API (api.telegram.org) – Used for: Sending security notifications to your configured Telegram bot – Triggered when: You enable Telegram notifications and configure a bot token and chat ID – Privacy Policy: https://telegram.org/privacy – Terms: https://telegram.org/tos IP Geolocation (ip-api.com) – Used for: Looking up geographical location of login attempts – Triggered when: Geolocation is enabled in settings (optional feature) – Privacy Policy: https://ip-api.com/docs/legal – Data sent: IP addresses only Cloudflare Turnstile (challenges.cloudflare.com) – Used for: Protecting the login form from bots – Triggered when: You enable Cloudflare Turnstile in settings and provide site keys – Privacy Policy: https://www.cloudflare.com/privacypolicy/ – Terms: https://www.cloudflare.com/website-terms/ All external service connections are optional and only occur when explicitly enabled by the administrator. No data is sent without your configuration and consent.

Lightweight, privacy-conscious pageview and event logging plugin that runs inside your own website. Quantely Activity is built to capture activity reliably under imperfect conditions through server-side recording and optional client-side signals, while supporting filtering for bots, unwanted pages, IP sources and selectable WordPress logged-in roles. Quantely Activity can be used for: Monitoring site behavior Reviewing traffic patterns Security and bot analysis Feeding downstream analytics layers Quantely Activity is turn-key: install it, and pageviews and events should begin appearing shortly after. Raw activity data is retained for a configurable short period, helping keep the plugin lightweight and privacy-conscious. What Quantely Activity is Quantely Activity is a capture and monitoring layer. It is designed to record activity on your site in a structured and reliable way, with a strong focus on signal capture and data integrity. Unlike many analytics tools, it does not focus on marketing analytics, attribution modelling, or behavioral profiling. It also does not rely solely on browser JavaScript. A server-side baseline helps ensure pageviews are still captured when scripts or beacons fail. Hybrid capture engine The plugin combines server-side pageview capture with optional browser-side signals. Typical flow: Browser request ↓ Server pageview baseline ↓ Browser attach (Beacon) – engagement pings – interaction events ↓ Correlation via pageview identifiers ↓ Bot classification and exclusions ↓ Deduplication and storage This architecture helps keep capture reliable under real-world conditions where browser-only tracking can miss signals. Event correlation and deduplication Quantely Activity links browser-side signals back to the pageview where they occurred. Engagement pings, clicks, form submissions, and similar events can be correlated to their originating pageview. Built-in deduplication helps avoid duplicate records when similar signals are captured from both browser and server-side sources. This keeps the activity stream more accurate and easier to interpret. Fully on-site All captured activity is stored in your own WordPress database. Quantely Activity does not send captured activity data to external services. IP addresses are never stored in plain form, and the plugin does not perform cross-site tracking. Privacy-aware design The plugin is designed with privacy-conscious principles in mind: No plain IP addresses stored Short configurable retention window Optional honoring of GPC / DNT signals No external tracking services Data remains on your own site This gives site owners visibility into activity while keeping capture local and controlled. Hooks Quantely Activity exposes a small developer API for integrations and downstream processing. qmon_hit_before_insert — Filter a normalized hit array before it is stored. qmon_hit_recorded — Action fired after a hit has been stored. This is the main integration point for forwarding or persisting captured records. qmon_event_normalize — Filter a normalized event payload before it is finalized. qmon_event_db_dedupe_window_sec — Filter the database deduplication window for events. qmon_bot_verdict — Filter the bot-classification verdict before it is finalized.