[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fyHMDYNqFF9DWCmu8p6vA9o6q-1RSi6yIuLyg5H4_bGQ":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"jesin","Jesin A","https:\u002F\u002Fprofiles.wordpress.org\u002Fjesin\u002F",3,670,85,30,84,"2026-04-04T09:06:18.478Z",[14,39,60],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":20,"downloaded":21,"rating":22,"num_ratings":23,"last_updated":24,"tested_up_to":25,"requires_at_least":26,"requires_php":27,"tags":28,"homepage":34,"download_link":35,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"custom-error-pages","Custom Error Pages","1.2","\u003Cp>WordPress offers inbuilt support for custom 404 pages on all themes. But what about custom pages for other common errors like 401 and 403? You end up seeing a bland error page of the Web Server.\u003C\u002Fp>\n\u003Cp>With this plugin you can easily create custom 401 and 403 error pages with any theme without writing a single line of code!!! And the best part is that you set it and forget it. Yes, you don’t have to do any changes even if you change themes. The heading and text you want on 401 and 403 error pages are displayed on the currently active theme.\u003C\u002Fp>\n\u003Ch4>Further Reading\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwebsistent.com\u002Fwordpress-custom-403-401-error-page\u002F\" rel=\"nofollow ugc\">Create WordPress 401 and 403 error pages\u003C\u002Fa> WITHOUT using this plugin\u003C\u002Fli>\n\u003Cli>The \u003Ca href=\"https:\u002F\u002Fwebsistent.com\u002Fwordpress-plugins\u002Fcustom-error-pages\u002F\" rel=\"nofollow ugc\">Custom Error Pages Plugin\u003C\u002Fa> official homepage.\u003C\u002Fli>\n\u003C\u002Ful>\n","Create custom 401 and 403 error pages with any WordPress theme without writing a single line of code, set it up and forget it.",600,20355,100,12,"2023-05-22T16:14:00.000Z","6.2.9","3.3.0","",[29,30,31,32,33],"401","403","404","error","errors","https:\u002F\u002Fwebsistent.com\u002Fwordpress-plugins\u002Fcustom-error-pages\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustom-error-pages.1.2.zip",0,null,"2026-03-15T15:16:48.613Z",{"slug":40,"name":41,"version":42,"author":5,"author_profile":6,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":27,"tags":52,"homepage":58,"download_link":59,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"mailgun-email-validator","Mailgun Email Validator","1.2.4.1","\u003Cp>Most email validators look for an \u003Ccode>@\u003C\u002Fcode> and a \u003Ccode>.\u003C\u002Fcode>(dot) some go further and blacklist certain domain names. But Mailgun’s Advanced email validation service goes deeper and looks for the existence of the domain name, presence of a \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMX_record\" rel=\"nofollow ugc\">MX record\u003C\u002Fa> and the custom ESP(Email Service Provider) grammar.\u003Cbr \u002F>\nThe grammar here is the rules defined by each email provider. For example, Yahoo Mail addresses can only contain letters, numbers, underscores, and one period.\u003Cbr \u002F>\nSo \u003Ccode>user.name.abc@yahoo.com\u003C\u002Fcode> perfectly passes the \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fis_email\" rel=\"nofollow ugc\">is_email()\u003C\u002Fa> function but can never exist as it contains more than one period. Such addresses can’t escape Mailgun’s Email validation.\u003C\u002Fp>\n\u003Ch4>Why use Mailgun’s email validation service?\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Performs the usual email syntax check.\u003C\u002Fli>\n\u003Cli>Checks the existence of the email domain. So \u003Ccode>user@some-random-characters.com\u003C\u002Fcode> can’t escape.\u003C\u002Fli>\n\u003Cli>Checks if the email domain has a MX record. So \u003Ccode>anything@example.com\u003C\u002Fcode> is caught.\u003C\u002Fli>\n\u003Cli>Checks if the username complies with the grammar of its ESP (Email Service provider). Eg Gmail doesn’t allow usernames less than 6 characters and hyphens so \u003Ccode>small@gmail.com\u003C\u002Fcode> and \u003Ccode>hyphen-user@gmail.com\u003C\u002Fcode> can’t get away.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Why use this plugin?\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Integrates with the \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fis_email\" rel=\"nofollow ugc\">is_email()\u003C\u002Fa> function of WordPress. So it works seamlessly with Contact Form 7, Jetpack\u002FGrunion contact forms, WordPress registration form and any form which uses the \u003Ccode>is_email()\u003C\u002Fcode> function.\u003C\u002Fli>\n\u003Cli>Kicks spam before it is inserted into the database\u003C\u002Fli>\n\u003Cli>Ensures that the commenting process is uninterrupted even if Mailgun suffers a \u003Ca href=\"http:\u002F\u002Fstatus.mailgun.com\" rel=\"nofollow ugc\">downtime\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Works completely transparent, nothing changes in the frontend\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This plugin requires a Mailgun Public API Key which can be obtained by \u003Ca href=\"https:\u002F\u002Fmailgun.com\u002Fsignup\" rel=\"nofollow ugc\">signing up at Mailgun\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>If you’re trying out this plugin on a local WAMP\u002FLAMP\u002FMAMP installation make sure your system is connected to the Internet for this plugin to contact Mailgun.\u003C\u002Fp>\n\u003Ch4>Available Languages\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>English\u003C\u002Fli>\n\u003Cli>Serbo-Croatian by \u003Ca href=\"http:\u002F\u002Fwww.webhostinghub.com\u002F\" rel=\"nofollow ugc\">Borisa Djuraskovic\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Spanish by \u003Ca href=\"http:\u002F\u002Fwww.webhostinghub.com\u002F\" rel=\"nofollow ugc\">Andrew Kurtis\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Further Reading\u003C\u002Fh4>\n\u003Cp>Read about Mailgun’s email validation service.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fblog.mailgun.com\u002Fpost\u002Ffree-email-validation-api-for-web-forms\u002F\" rel=\"nofollow ugc\">http:\u002F\u002Fblog.mailgun.com\u002Fpost\u002Ffree-email-validation-api-for-web-forms\u002F\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fblog.mailgun.com\u002Fpost\u002Fweekly-product-update-improvements-to-email-validation-api\u002F\" rel=\"nofollow ugc\">http:\u002F\u002Fblog.mailgun.com\u002Fpost\u002Fweekly-product-update-improvements-to-email-validation-api\u002F\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fmailgun.github.io\u002Fvalidator-demo\u002F\" rel=\"nofollow ugc\">Mailgun Address Validator demo\u003C\u002Fa> and its \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmailgun\u002Fvalidator-demo\u002Ftree\u002Fgh-pages\" rel=\"nofollow ugc\">source code\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>The \u003Ca href=\"https:\u002F\u002Fwebsistent.com\u002Fwordpress-plugins\u002Fmailgun-email-validator\u002F\" rel=\"nofollow ugc\">Mailgun Email Validator Plugin\u003C\u002Fa> official homepage.\u003C\u002Fli>\n\u003C\u002Ful>\n","Kick spam with a highly advanced email validation in comment forms, user registration and contact forms using Mailgun's Email validation service.",60,11426,82,25,"2017-11-25T14:21:00.000Z","4.9.29","3.1.0",[53,54,55,56,57],"anti-spam","comments","email-validation","spam","validation","https:\u002F\u002Fwebsistent.com\u002Fwordpress-plugins\u002Fmailgun-email-validator\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmailgun-email-validator.1.2.4.1.zip",{"slug":61,"name":62,"version":63,"author":5,"author_profile":6,"description":64,"short_description":65,"active_installs":66,"downloaded":67,"rating":68,"num_ratings":69,"last_updated":70,"tested_up_to":50,"requires_at_least":51,"requires_php":27,"tags":71,"homepage":77,"download_link":78,"security_score":9,"vuln_count":36,"unpatched_count":36,"last_vuln_date":37,"fetched_at":38},"http-digest-auth","HTTP Digest Authentication","1.2.1","\u003Cp>This plugin adds an additional layer of protection for the \u003Cstrong>wp-login.php\u003C\u002Fstrong> page using \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FDigest_access_authentication\" rel=\"nofollow ugc\">HTTP Digest Authentication\u003C\u002Fa> with the PHP \u003Ca href=\"http:\u002F\u002Fphp.net\u002Fheader\" rel=\"nofollow ugc\">header()\u003C\u002Fa> function.\u003Cbr \u002F>\nSo it doesn’t require configuring web server files like \u003Cem>.htaccess\u003C\u002Fem> or \u003Ca href=\"https:\u002F\u002Fwebsistent.com\u002Ftools\u002Fhtdigest-generator-tool\u002F\" rel=\"nofollow ugc\">\u003Cem>.htdigest\u003C\u002Fem>\u003C\u002Fa> and works on all web hosting environments.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Important:\u003C\u002Fstrong> If you already have a plugin which does HTTP Authentication please deactivate it before activating this plugin. Similarly if you have configured your web server to do HTTP authentication on the wp-login.php file please remove it before using this plugin.\u003C\u002Fp>\n\u003Cp>If you are using FastCGI PHP this plugin may keep prompting for the credentials even if you enter the right pair, in this case use the following in your \u003Cstrong>\u003Ccode>.htaccess\u003C\u002Fcode>\u003C\u002Fstrong> file\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003CIfModule mod_setenvif.c>\nSetEnvIfNoCase ^Authorization$ \"(.+)\" PHP_AUTH_DIGEST=$1\n\u003C\u002FIfModule>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Advantages of HTTP Digest Authentication\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Digest Authentication is very much safer than HTTP Basic Authentication whose credentials can be easily decoded with a \u003Ca href=\"http:\u002F\u002Fwww.base64decode.org\u002F\" rel=\"nofollow ugc\">base64 decoder\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>From Wikipedia on \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FBasic_access_authentication\" rel=\"nofollow ugc\">HTTP Basic Authentication\u003C\u002Fa>:\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote>\n\u003Cp>\u003Cem>The BA (Basic Authentication) mechanism provides no confidentiality protection for the transmitted credentials. They are merely encoded with BASE64 in transit, but not encrypted or hashed in any way.\u003C\u002Fem>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cul>\n\u003Cli>Digest Authentication on the other hand uses \u003Ca href=\"https:\u002F\u002Fwebsistent.com\u002Ftools\u002Fmd5-encryption-tool\u002F\" rel=\"nofollow ugc\">MD5\u003C\u002Fa> on the credentials making it “one way” \u003C\u002Fli>\n\u003Cli>Uses server and client \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FCryptographic_nonce\" rel=\"nofollow ugc\">nonce\u003C\u002Fa>s to prevent replay attacks\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Features of the HTTP Digest Auth plugin\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Works using PHP header() function and doesn’t require modification of service config files (like .htaccess, nginx.conf etc)\u003C\u002Fli>\n\u003Cli>Supports HTTP credentials for each WordPress user\u003C\u002Fli>\n\u003Cli>Clears the HTTP Digest credentials when the user logs out of WordPress (more on this in the FAQ)\u003C\u002Fli>\n\u003Cli>Verifies if both the HTTP and WordPress credentials are of the same user (this is the default behavior and can be changed)\u003C\u002Fli>\n\u003Cli>Works on all major Web Servers (Tested on Apache, Nginx and Lighttpd)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Plugin Behavior\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>When this plugin is activated for the first time all WordPress users will have the following Digest credentials\u003Cbr \u002F>\nUsername: \u003CWordPress username>\u003Cbr \u002F>\nPassword: password\u003Cbr \u002F>\nThis can be changed from \u003Cstrong>Users > Your Profile\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>After activating this plugin for the first time you’ll be prompted for HTTP credentials when you logout\u003C\u002Fli>\n\u003Cli>Similarly if you change your HTTP username or password you’ll be prompted for this when you logout\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Available languages\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>English\u003C\u002Fli>\n\u003Cli>Serbo-Croatian by \u003Ca href=\"http:\u002F\u002Fwww.webhostinghub.com\u002F\" rel=\"nofollow ugc\">Borisa Djuraskovic\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The \u003Ca href=\"https:\u002F\u002Fwebsistent.com\u002Fwordpress-plugins\u002Fhttp-digest-authentication\u002F\" rel=\"nofollow ugc\">HTTP Digest Authentication Plugin\u003C\u002Fa> official homepage.\u003C\u002Fp>\n","Protect your wp-login.php page with HTTP Digest Authentication without the need of adding web server modules or changing config files.",10,4957,80,5,"2017-11-25T14:25:00.000Z",[72,73,74,75,76],"auth","authenticate","hacking","http-digest","login","https:\u002F\u002Fwebsistent.com\u002Fwordpress-plugins\u002Fhttp-digest-authentication\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhttp-digest-auth.1.2.1.zip"]