Login Security with Telegram Alerts
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.
Web-Art Login Shield with reCAPTCHA
Web-Art Login Shield with reCAPTCHA protects WordPress authentication, Elementor Login widgets and Elementor Forms. It provides optional Google reCAPTCHA v2/v3, IP lockouts, Advanced login URL protection, IP blocking and REST/XML-RPC protection. It preserves WordPress core authentication logic. No ads, author telemetry or external dashboard. All modules are opt-in and disabled by default. Key Features reCAPTCHA v2/v3 selectable v2 checkbox or v3 score-based verification protection for wp-login.php, native WordPress password reset requests, Elementor Login and Elementor Forms server-side token, action, score and hostname validation where applicable configurable v3 score threshold one active type at a time configuration verification before activation Elementor support protection for Elementor Login, classic Elementor Pro Forms and Atomic Forms classic forms containing native Elementor reCAPTCHA fields are skipped to avoid duplication v2 alignment controls login errors and lockouts remain inside the Login widget dynamic content and Elementor popup support Login Protect per-IP failed-attempt counting and temporary lockouts safe concurrent-request handling active-lockout countdown local security event log with bounded retention optional REST API, Application Password and XML-RPC protection independent operation with or without reCAPTCHA Advanced login URL optional custom login endpoint protection of default login routes while preserving required public actions logout and password-link compatibility emergency wp-config.php recovery constant IP allowlists and blocking separate reCAPTCHA allowlist and Login Protect trusted IP list permanent IP blocking for public site requests with HTTP 403 optional IP | reason notes XML-RPC hardening Optional blocking of: pingback.ping pingback.extensions.getPingbacks system.multicall Security Model Compatibility scope: the Elementor Forms integration supports the classic Elementor Pro Form widget and Atomic Forms with reCAPTCHA v2 and v3. Atomic submissions are verified server-side before form actions run, and internal CAPTCHA fields are removed from submission data. Native WooCommerce My Account/checkout login, registration and password reset forms do not currently have a dedicated reCAPTCHA integration. Login Protect’s interactive attempt detection covers WordPress login and this plugin’s Elementor Login AJAX flow, not native WooCommerce login. REST protection refers to WordPress authentication (including Application Passwords), not a dedicated WooCommerce consumer-key authentication integration. Protected flows use fail-closed handling. If an enabled check cannot be completed safely, the request is rejected instead of bypassing protection. Login Protect preserves active lockouts and safely handles concurrent requests. Setting Maximum login attempts or Lockout duration to 0 disables lockout enforcement. All modules remain disabled until enabled. Recovery constants are available in wp-config.php for selected modules. External Services This plugin integrates with Google reCAPTCHA v2 and v3, services provided by Google LLC. reCAPTCHA is disabled by default. Google scripts or verification requests are used only after an administrator enables reCAPTCHA or runs a settings-page verification test. Google’s reCAPTCHA JavaScript (https://www.google.com/recaptcha/api.js) may load on protected wp-login.php requests, pages containing protected Elementor widgets or forms, and the settings page during a verification test. Allowlisted visitors bypass frontend loading where applicable. When reCAPTCHA runs, the visitor’s browser connects directly to Google. Google may process browser, device and interaction information and may set the necessary _GRECAPTCHA cookie under its policies. For server-side verification, the plugin sends the token, configured Secret Key and visitor IP address when available to Google’s siteverify endpoint. It does not include usernames, passwords, email addresses or form contents in that request. The plugin sends no telemetry, analytics or usage data to its author. Google policies: https://policies.google.com/privacy https://policies.google.com/terms Privacy Locally stored security data may include: IP addresses, failed-attempt counts and lockout timestamps a username or email associated with an IP lockout recent events containing an IP address, username or email, source, type and timestamp the latest reCAPTCHA configuration or transport error used for diagnostics permanent IP blocklist entries and optional notes Inactive Login Protect entries become eligible for deletion after seven days. Active lockouts remain until expiry. The event log is limited to 30 entries and 30 days. WordPress privacy tools export or erase records matched to the requested email address or associated account. Unmatched IP-only records remain subject to retention and administrator cleanup. Permanent blocklist entries remain until removed by an administrator. Plugin data can be removed during uninstall when uninstall cleanup is enabled. Legal reCAPTCHA is a trademark of Google LLC. Elementor is a trademark of Elementor Ltd. This plugin is not affiliated with, endorsed by, or sponsored by Google LLC or Elementor Ltd.
