msgid ""
msgstr ""
"Project-Id-Version: Plugins - All In One WP Security & Firewall - Development (trunk)\n"
"POT-Creation-Date: \n"
"PO-Revision-Date: 2019-06-15 09:34+1000\n"
"Last-Translator: \n"
"Language-Team: \n"
"Language: nl\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
"X-Generator: Poedit 2.2.3\n"

#. Plugin Name of the plugin
msgid "All In One WP Security"
msgstr "All In One WP Security"

#. Plugin URI of the plugin
msgid "https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/"
msgstr "https://www.tipsandtricks-hq.com/wordpress-security-and-firewall-plugin"

#. Description of the plugin
msgid "All round best WordPress security plugin!"
msgstr "De beste all-round WordPress beveiligings-plug-in!"

#. Author of the plugin
msgid "All In One WP Security & Firewall Team"
msgstr "Tips and Tricks HQ, Peter Petreski, Ruhul, Ivy"

#. Author URI of the plugin
msgid "https://teamupdraft.com/"
msgstr "https://www.tipsandtricks-hq.com/"

#: admin/general/wp-security-list-table.php:483
msgid "Are you sure you want to perform this bulk action?"
msgstr ""

#: admin/wp-security-admin-init.php:259
msgid "Unexpected response:"
msgstr ""

#: admin/wp-security-admin-init.php:290
msgid "Enjoyed %1$s? Please leave us a %2$s rating. We really appreciate your support!"
msgstr ""

#: admin/wp-security-admin-init.php:414
#: classes/wp-security-two-factor-login.php:95
msgid "WP Security"
msgstr "WP-beveiliging"

#: admin/wp-security-admin-init.php:415
#: admin/wp-security-dashboard-menu.php:26
#: admin/wp-security-dashboard-menu.php:76
msgid "Dashboard"
msgstr "Dashboard"

#: admin/wp-security-admin-init.php:416
#: admin/wp-security-settings-menu.php:95
msgid "Settings"
msgstr "Instellingen"

#: admin/wp-security-admin-init.php:417
msgid "User Accounts"
msgstr "Gebruikersaccounts"

#: admin/wp-security-admin-init.php:418
msgid "User Login"
msgstr "Gebruikerslogin"

#: admin/wp-security-admin-init.php:419
msgid "User Registration"
msgstr "Gebruikersregistratie"

#: admin/wp-security-admin-init.php:420
msgid "Database Security"
msgstr "Databasebeveiliging"

#: admin/wp-security-admin-init.php:424
msgid "Filesystem Security"
msgstr "Bestandsbeveiliging"

#: admin/wp-security-admin-init.php:429
msgid "Blacklist Manager"
msgstr "Blacklist-manager"

#: admin/wp-security-admin-init.php:434
#: admin/wp-security-firewall-menu.php:60
msgid "Firewall"
msgstr "Firewall"

#: admin/wp-security-admin-init.php:436
msgid "Brute Force"
msgstr "Brute Force"

#: admin/wp-security-admin-init.php:437
msgid "Spam Prevention"
msgstr "SPAM voorkomen"

#: admin/wp-security-admin-init.php:441
#: admin/wp-security-filescan-menu.php:53
msgid "Scanner"
msgstr "Scanner"

#: admin/wp-security-admin-init.php:443
#: admin/wp-security-maintenance-menu.php:51
msgid "Maintenance"
msgstr "Onderhoud"

#: admin/wp-security-admin-init.php:444
#: admin/wp-security-misc-options-menu.php:57
msgid "Miscellaneous"
msgstr "Overige"

#: admin/wp-security-admin-init.php:445
#: admin/wp-security-tools-menu.php:64
msgid "Tools"
msgstr ""

#: admin/wp-security-admin-init.php:457
msgid "Premium Upgrade"
msgstr ""

#: admin/wp-security-admin-menu.php:67
msgid "Settings successfully updated."
msgstr "Instelling zijn succesvol bijgewerkt."

#: admin/wp-security-admin-menu.php:77
msgid "Successfully deleted the selected record(s)."
msgstr ""

#: admin/wp-security-admin-menu.php:86
msgid "Failed to delete the selected record(s)."
msgstr ""

#: admin/wp-security-blacklist-menu.php:25
msgid "Ban users"
msgstr "Gebruikers verbannen"

#: admin/wp-security-blacklist-menu.php:51
msgid "Blacklist manager"
msgstr "Blacklist-manager"

#: admin/wp-security-blacklist-menu.php:132
#: admin/wp-security-firewall-menu.php:1233
#: admin/wp-security-list-404.php:234
#: admin/wp-security-list-comment-spammer-ip.php:205
msgid "The plugin was unable to write to the .htaccess file. Please edit file manually."
msgstr "Plugin kon niet schrijven naar het .htaccess-bestand. Gelieve het bestand handmatig te bewerken."

#: admin/wp-security-blacklist-menu.php:139
msgid "Ban IPs or user agents"
msgstr "IPs van User Agents verbannen"

#: admin/wp-security-blacklist-menu.php:142
msgid "The All In One WP Security Blacklist feature gives you the option of banning certain host IP addresses or ranges and also user agents."
msgstr "De All In One WP Security Blacklist-functie geeft u de mogelijkheid om bepaalde IP-hostadressen, bereiken en providers van de gebruiker te weren."

#: admin/wp-security-blacklist-menu.php:143
msgid "This feature will deny total site access for users which have IP addresses or user agents matching those which you have configured in the settings below."
msgstr "Deze functie zal de toegang tot de site ontzeggen aan gebruikers met bepaalde IP-adressen of providers die overeenkomen met onderstaande instellingen."

#: admin/wp-security-blacklist-menu.php:144
msgid "The plugin achieves this by making appropriate modifications to your .htaccess file."
msgstr "De plugin bereikt dit door het maken van passende wijzigingen aan uw .htaccess-bestand."

#: admin/wp-security-blacklist-menu.php:145
msgid "By blocking people, you are using the most secure first line of defence, which denies all access to blacklisted visitors as soon as they hit your hosting server."
msgstr "Door mensen via het. htaccess-bestand te blokkeren gebruikt u de veiligste eerste lijn van defensie, die alle toegang voor bezoekers die op de zwarte lijst staan blokkeert zodra zij uw server benaderen."

#: admin/wp-security-blacklist-menu.php:154
#: admin/wp-security-firewall-menu.php:1055
#: templates/may-also-like.php:20
msgid "All In One WP Security & Firewall Premium"
msgstr ""

#: admin/wp-security-blacklist-menu.php:155
#: admin/wp-security-firewall-menu.php:1056
msgid "You may also be interested in %s."
msgstr ""

#: admin/wp-security-blacklist-menu.php:156
#: admin/wp-security-firewall-menu.php:1057
msgid "This plugin adds a number of extra features including %s and %s."
msgstr ""

#: admin/wp-security-blacklist-menu.php:156
#: admin/wp-security-firewall-menu.php:1057
msgid "smart 404 blocking"
msgstr ""

#: admin/wp-security-blacklist-menu.php:156
#: admin/wp-security-firewall-menu.php:1057
msgid "country IP blocking"
msgstr ""

#: admin/wp-security-blacklist-menu.php:170
msgid "IP hosts and user agent blacklist settings"
msgstr "IP-hosts en User Agent blacklist-instellingen"

#: admin/wp-security-blacklist-menu.php:182
#: admin/wp-security-brute-force-menu.php:193
#: admin/wp-security-brute-force-menu.php:331
msgid "must read this message"
msgstr ""

#: admin/wp-security-blacklist-menu.php:183
#: admin/wp-security-brute-force-menu.php:194
msgid "This feature can lock you out of admin if it doesn't work correctly on your site. You %s before activating this feature."
msgstr "Met deze functie kunt u de beheerder blokkeren als deze niet correct werkt op uw site . U %s voordat u deze functie activeert."

#: admin/wp-security-blacklist-menu.php:189
msgid "Enable IP or user agent blacklisting"
msgstr "Gebruik maken van IP- of User Agent blacklisten"

#: admin/wp-security-blacklist-menu.php:192
msgid "Check this if you want to enable the banning (or blacklisting) of selected IP addresses and/or user agents specified in the settings below"
msgstr "Selecteer dit als u het verbannen (of blacklisting) van de geselecteerde IP-adressen en/of user agents genoemd in de onderstaande instellingen wilt inschakelen"

#: admin/wp-security-blacklist-menu.php:196
msgid "Enter IP addresses:"
msgstr "Vul IP-adressen In:"

#: admin/wp-security-blacklist-menu.php:200
msgid "Enter one or more IP addresses or IP ranges."
msgstr "Vul een of meerdere IP-adressen of IP-bereiken in."

#: admin/wp-security-blacklist-menu.php:205
msgid "Enter user agents:"
msgstr "Vul User Agents in:"

#: admin/wp-security-blacklist-menu.php:210
msgid "Enter one or more user agent strings."
msgstr "Vul een of meerdere user agent strings in."

#: admin/wp-security-blacklist-menu.php:211
#: admin/wp-security-brute-force-menu.php:374
#: admin/wp-security-brute-force-menu.php:408
#: admin/wp-security-brute-force-menu.php:431
#: admin/wp-security-brute-force-menu.php:452
#: admin/wp-security-filescan-menu.php:309
#: admin/wp-security-filescan-menu.php:326
#: admin/wp-security-firewall-menu.php:175
#: admin/wp-security-firewall-menu.php:212
#: admin/wp-security-firewall-menu.php:232
#: admin/wp-security-firewall-menu.php:258
#: admin/wp-security-firewall-menu.php:385
#: admin/wp-security-firewall-menu.php:415
#: admin/wp-security-firewall-menu.php:446
#: admin/wp-security-firewall-menu.php:474
#: admin/wp-security-firewall-menu.php:503
#: admin/wp-security-firewall-menu.php:681
#: admin/wp-security-firewall-menu.php:699
#: admin/wp-security-firewall-menu.php:737
#: admin/wp-security-firewall-menu.php:868
#: admin/wp-security-firewall-menu.php:1087
#: admin/wp-security-firewall-menu.php:1110
#: admin/wp-security-spam-menu.php:186
#: admin/wp-security-spam-menu.php:221
#: admin/wp-security-spam-menu.php:390
#: admin/wp-security-spam-menu.php:430
#: admin/wp-security-user-login-menu.php:362
#: templates/info/ip-address-ip-range-info.php:2
#: templates/menus/settings/advanced-settings.php:63
msgid "More info"
msgstr "Meer informatie"

#: admin/wp-security-blacklist-menu.php:214
msgid "Each user agent string must be on a new line."
msgstr "Elke user agent string moet op een nieuwe regel beginnen."

#: admin/wp-security-blacklist-menu.php:215
msgid "Example 1 - A single user agent string to block:"
msgstr "Voorbeeld 1 - Een enkele user agent string om te blokkeren:"

#: admin/wp-security-blacklist-menu.php:217
msgid "Example 2 - A list of more than 1 user agent strings to block"
msgstr "Voorbeeld 2 - Een lijst van meerdere user agent strings om te blokkeren"

#: admin/wp-security-blacklist-menu.php:225
#: admin/wp-security-brute-force-menu.php:213
#: admin/wp-security-brute-force-menu.php:686
#: admin/wp-security-brute-force-menu.php:806
#: admin/wp-security-brute-force-menu.php:868
#: admin/wp-security-filescan-menu.php:351
#: admin/wp-security-filesystem-menu.php:242
#: admin/wp-security-firewall-menu.php:945
#: admin/wp-security-firewall-menu.php:1129
#: admin/wp-security-misc-options-menu.php:167
#: admin/wp-security-misc-options-menu.php:218
#: admin/wp-security-misc-options-menu.php:278
#: admin/wp-security-settings-menu.php:619
#: admin/wp-security-settings-menu.php:680
#: admin/wp-security-spam-menu.php:233
#: admin/wp-security-spam-menu.php:407
#: admin/wp-security-spam-menu.php:526
#: admin/wp-security-spam-menu.php:588
#: admin/wp-security-user-login-menu.php:384
#: admin/wp-security-user-login-menu.php:422
#: admin/wp-security-user-login-menu.php:601
#: admin/wp-security-user-login-menu.php:788
#: admin/wp-security-user-registration-menu.php:150
#: admin/wp-security-user-registration-menu.php:242
#: admin/wp-security-user-registration-menu.php:305
#: templates/menus/settings/advanced-settings.php:217
msgid "Save settings"
msgstr "Bewaar instellingen"

#: admin/wp-security-brute-force-menu.php:33
#: admin/wp-security-brute-force-menu.php:759
#: admin/wp-security-dashboard-menu.php:651
msgid "Rename login page"
msgstr "Hernoem loginpagina"

#: admin/wp-security-brute-force-menu.php:34
#: admin/wp-security-brute-force-menu.php:154
msgid "Cookie based brute force prevention"
msgstr "Brute Force voorkomen met cookies"

#: admin/wp-security-brute-force-menu.php:35
#: classes/grade-system/wp-security-feature-item-manager.php:105
msgid "Login CAPTCHA"
msgstr "Login captcha"

#: admin/wp-security-brute-force-menu.php:36
#: admin/wp-security-brute-force-menu.php:746
msgid "Login whitelist"
msgstr "Login whitelist"

#: admin/wp-security-brute-force-menu.php:37
msgid "Honeypot"
msgstr "Honeypot"

#: admin/wp-security-brute-force-menu.php:67
msgid "Brute force"
msgstr "Brute Force"

#: admin/wp-security-brute-force-menu.php:105
msgid "Please enter a value for your login page slug."
msgstr "Vul een waarde in voor de slug van jouw loginpagina."

#: admin/wp-security-brute-force-menu.php:109
msgid "You cannot use the value \"wp-admin\" for your login page slug."
msgstr "Je kan de waarde \"wp-admin\" niet gebruiken voor je loginpagina."

#: admin/wp-security-brute-force-menu.php:111
msgid "You must use alpha numeric characters for your login page slug."
msgstr "U moet gebruik maken van alfa-numerieke tekens voor de slug van uw loginpagina."

#: admin/wp-security-brute-force-menu.php:116
#: admin/wp-security-filescan-menu.php:174
#: admin/wp-security-firewall-menu.php:151
#: admin/wp-security-firewall-menu.php:1011
#: admin/wp-security-spam-menu.php:101
#: admin/wp-security-spam-menu.php:270
#: admin/wp-security-spam-menu.php:302
#: admin/wp-security-user-login-menu.php:184
#: admin/wp-security-user-login-menu.php:553
#: templates/partials/non-apache-feature-notice.php:9
msgid "Attention:"
msgstr ""

#: admin/wp-security-brute-force-menu.php:133
msgid "Could not delete the Cookie-based directives from the .htaccess file. Please check the file permissions."
msgstr "Kan de op cookies gebaseerde richtlijnen niet verwijderen uit het. htaccess-bestand. Controleer de bestandspermissies."

#: admin/wp-security-brute-force-menu.php:155
msgid "Login page white list"
msgstr ""

#: admin/wp-security-brute-force-menu.php:156
msgid "An effective Brute Force prevention technique is to change the default WordPress login page URL."
msgstr "Een effectieve Brute Force Prevention techniek is het veranderen van de URL van de standaard WordPress-loginpagina."

#: admin/wp-security-brute-force-menu.php:157
msgid "Normally if you wanted to login to WordPress you would type your site's home URL followed by wp-login.php."
msgstr "Normaal als je wilt inloggen op WordPress dan zou je de site-URL ingeven gevolgd door wp-login.php."

#: admin/wp-security-brute-force-menu.php:158
msgid "This feature allows you to change the login URL by setting your own slug and renaming the last portion of the login URL which contains the <strong>wp-login.php</strong> to any string that you like."
msgstr "Met deze functie kunt u de login-URL wijzigen door uw eigen slug in te stellen en het laatste deel van de login-URL die de <strong>wp-login.php</strong> bevat te hernoemen naar iedere tekenreeks die u wilt."

#: admin/wp-security-brute-force-menu.php:159
msgid "By doing this, malicious bots and hackers will not be able to access your login page because they will not know the correct login page URL."
msgstr "Door dit te doen, zullen kwaadaardige bots en hackers niet in staat zijn om toegang te krijgen tot uw loginpagina, omdat ze de juiste loginpagina-URL niet weten."

#: admin/wp-security-brute-force-menu.php:161
msgid "You may also be interested in the following alternative brute force prevention features:"
msgstr "U kunt ook geïnteresseerd zijn in de volgende alternatieve brute force preventiemogelijkheden:"

#: admin/wp-security-brute-force-menu.php:172
msgid "Your WordPress login page URL has been renamed."
msgstr "Je WordPress loginpagina-URL is veranderd."

#: admin/wp-security-brute-force-menu.php:173
msgid "Your current login URL is:"
msgstr "Je huidige login-URL is:"

#: admin/wp-security-brute-force-menu.php:181
msgid "Rename login page settings"
msgstr "Hernoem loginpagina-instellingen"

#: admin/wp-security-brute-force-menu.php:195
msgid "NOTE: If you are hosting your site on WPEngine or a provider which performs server caching, you will need to ask the host support people to NOT cache your renamed login page."
msgstr "Opmerking: Als u uw site host op WPEngine of een provider die server caching uitvoert, zult u de personen van host ondersteuning moeten vragen om uw hernoemde loginpagina niet in een cache te plaatsen."

#: admin/wp-security-brute-force-menu.php:200
msgid "Enable rename login page feature"
msgstr "Hernoem loginpagina gebruiken"

#: admin/wp-security-brute-force-menu.php:203
msgid "Check this if you want to enable the rename login page feature"
msgstr "Vink dit aan als je de loginpagina wilt hernoemen"

#: admin/wp-security-brute-force-menu.php:207
msgid "Login page URL"
msgstr "Loginpagina-URL"

#: admin/wp-security-brute-force-menu.php:209
msgid "Enter a string which will represent your secure login page slug. You are encouraged to choose something which is hard to guess and only you will remember."
msgstr ""

#: admin/wp-security-brute-force-menu.php:243
msgid "Settings have not been saved - your secret word must consist only of alphanumeric characters, ie, letters and/or numbers only."
msgstr "Instellingen niet opgeslagen - uw geheime woord mag alleen bestaan uit alfanumerieke tekens, dat wil zeggen, letters en/of cijfers."

#: admin/wp-security-brute-force-menu.php:257
msgid "You have successfully enabled the cookie based brute force prevention feature"
msgstr "U hebt de op cookie-gebaseerde Brute Force Prevention-functie met succes ingeschakeld"

#: admin/wp-security-brute-force-menu.php:258
msgid "From now on you will need to log into your WP Admin using the following URL:"
msgstr "Vanaf nu moet u zich aanmelden bij uw WP-admin met behulp van de volgende URL:"

#: admin/wp-security-brute-force-menu.php:260
msgid "It is important that you save this URL value somewhere in case you forget it, OR,"
msgstr "Het is belangrijk dat u deze URL-waarde ergens opslaat voor het geval dat je het vergeet, of,"

#: admin/wp-security-brute-force-menu.php:261
msgid "simply remember to add a \"?%s=1\" to your current site URL address."
msgstr "vergeet niet om een \"?%s = 1\" toe te voegen aan uw huidige site-URL."

#: admin/wp-security-brute-force-menu.php:265
msgid "You have successfully saved cookie based brute force prevention feature settings."
msgstr "Je hebt met succes de op cookie-gebaseerde brute force preventiefunctie-instellingen opgslagen."

#: admin/wp-security-brute-force-menu.php:295
msgid "Brute force prevention firewall settings"
msgstr "Brute Force firewall-instellingen"

#: admin/wp-security-brute-force-menu.php:300
msgid "A Brute Force Attack is when a hacker tries many combinations of usernames and passwords until they succeed in guessing the right combination."
msgstr "Een brute force aanval is een poging van een hacker om verschillende combinaties van gebruikersnaam en wachtwoord te proberen totdat hij de juiste combinatie raadt."

#: admin/wp-security-brute-force-menu.php:301
msgid "Due to the fact that at any one time there may be many concurrent login attempts occurring on your site via malicious automated robots, this also has a negative impact on your server's memory and performance."
msgstr "Vanwege het feit dat er op een gegeven moment veel gelijktijdige aanmeldingspogingen kunnen zijn, die zich op uw site via kwaadaardige geautomatiseerde robots aanmelden, heeft dit ook een negatieve invloed op het geheugen van uw server en de prestaties."

#: admin/wp-security-brute-force-menu.php:302
msgid "The features in this tab will stop the majority of brute force login attacks thus providing even better protection for your WP login page."
msgstr ""

#: admin/wp-security-brute-force-menu.php:307
#: admin/wp-security-firewall-menu.php:654
msgid "backup"
msgstr ""

#: admin/wp-security-brute-force-menu.php:308
msgid "video tutorial"
msgstr ""

#: admin/wp-security-brute-force-menu.php:309
msgid "To learn more about how to use this feature, please watch the following %s."
msgstr ""

#: admin/wp-security-brute-force-menu.php:310
#: admin/wp-security-brute-force-menu.php:758
msgid "Cookie-Based Brute Force Login Prevention"
msgstr ""

#: admin/wp-security-brute-force-menu.php:320
#: admin/wp-security-user-login-menu.php:253
msgid "Cookie based brute force login prevention"
msgstr "Brute Force voorkomen via cookies"

#: admin/wp-security-brute-force-menu.php:331
msgid "This feature can lock you out of admin if it doesn't work correctly on your site. You <a href=\"https://www.tipsandtricks-hq.com/wordpress-security-and-firewall-plugin#advanced_features_note\" target=\"_blank\">"
msgstr ""

#: admin/wp-security-brute-force-menu.php:342
msgid "The cookie test was successful. You can now enable this feature."
msgstr "De cookietest was succesvol. Je kan deze optie nu gaan gebruiken."

#: admin/wp-security-brute-force-menu.php:350
msgid "The cookie test failed on this server. Consequently, this feature cannot be used on this site."
msgstr ""

#: admin/wp-security-brute-force-menu.php:357
msgid "Before using this feature, you must perform a cookie test first."
msgstr ""

#: admin/wp-security-brute-force-menu.php:359
msgid "This ensures that your browser cookie is working correctly and that you won't lock yourself out."
msgstr ""

#: admin/wp-security-brute-force-menu.php:364
msgid "Perform cookie test"
msgstr "Cookietest uitvoeren"

#: admin/wp-security-brute-force-menu.php:370
#: classes/grade-system/wp-security-feature-item-manager.php:103
msgid "Enable brute force attack prevention"
msgstr "Brute Force aanvallen voorkomen"

#: admin/wp-security-brute-force-menu.php:373
msgid "Check this if you want to protect your login page from Brute Force Attack."
msgstr "Vink dit aan als je jouw loginpagina wil beschermen tegen Brute Force aanvallen."

#: admin/wp-security-brute-force-menu.php:378
msgid "This feature will deny access to your WordPress login page for all people except those who have a special cookie in their browser."
msgstr "Deze optie weigert toegang tot de WordPress-loginpagina voor iedereen behalve degene die een bepaalde cookie in hun browser hebben."

#: admin/wp-security-brute-force-menu.php:380
msgid "To use this feature do the following:"
msgstr "Om deze optie te gebruiken moet je het volgende doen:"

#: admin/wp-security-brute-force-menu.php:382
msgid "1) Enable the checkbox."
msgstr "1) Gebruik de checkbox."

#: admin/wp-security-brute-force-menu.php:384
msgid "2) Enter a secret word consisting of alphanumeric characters which will be difficult to guess. This secret word will be useful whenever you need to know the special URL which you will use to access the login page (see point below)."
msgstr "2) Voer een geheim woord, bestaande uit alfanumerieke tekens in die moeilijk is om te raden. Dit geheime woord zal nuttig zijn wanneer u de speciale URL moet kennen die u zult gebruiken om toegang te hebben tot de login pagina (zie punt hieronder)."

#: admin/wp-security-brute-force-menu.php:386
msgid "3) You will then be provided with a special login URL. You will need to use this URL to login to your WordPress site instead of the usual login URL. NOTE: The system will deposit a special cookie in your browser which will allow you access to the WordPress administration login page."
msgstr "3) u wordt dan voorzien van een speciale inlog-URL. U moet deze URL gebruiken om in te loggen op uw WordPress-site in plaats van de gebruikelijke login-URL. Opmerking: het systeem zal een speciale cookie in uw browser plaatsen, die u toegang zal verlenen tot de WordPress administratie loginpagina."

#: admin/wp-security-brute-force-menu.php:388
msgid "Any person trying to access your login page who does not have the special cookie in their browser will be automatically blocked."
msgstr "Elke persoon die toegang probeert te krijgen tot uw aanmeldingspagina die de speciale cookie niet in de browser heeft, wordt automatisch geblokkeerd."

#: admin/wp-security-brute-force-menu.php:395
msgid "Secret word"
msgstr "Geheim woord"

#: admin/wp-security-brute-force-menu.php:397
msgid "Choose a secret word consisting of alphanumeric characters which you can use to access your special URL. Your are highly encouraged to choose a word which will be difficult to guess."
msgstr "Kies een geheim woord dat bestaat uit letters en cijfers en die u kunt gebruiken om toegang te krijgen tot uw speciale URL. U wordt aangeraden om een woord te kiezen dat moeilijk te raden is."

#: admin/wp-security-brute-force-menu.php:401
msgid "Re-direct URL"
msgstr "URL doorverwijzen"

#: admin/wp-security-brute-force-menu.php:405
msgid "Specify a URL to redirect a hacker to when they try to access your WordPress login page."
msgstr "Geef een URL op waarnaar een hacker wordt omgeleid als ze proberen toegang tot uw WordPress-loginpagina te krijgen."

#: admin/wp-security-brute-force-menu.php:412
msgid "The URL specified here can be any site's URL and does not have to be your own. For example you can be as creative as you like and send hackers to the CIA or NSA home page."
msgstr "De URL die je hier invult kan elke site zijn en hoeft niet jouw eigen te zijn. Je kan bijvoorbeeld heel creatief zijn en de hackers naar de CIA of NSA homepagina sturen."

#: admin/wp-security-brute-force-menu.php:414
msgid "This field will default to: http://127.0.0.1 if you do not enter a value."
msgstr "Dit veld zal standaard http://127.0.0.1 gebruiken als je niks invult."

#: admin/wp-security-brute-force-menu.php:416
msgid "Useful Tip:"
msgstr "Handige tip:"

#: admin/wp-security-brute-force-menu.php:418
msgid "It's a good idea to not redirect attempted brute force login attempts to your site because it increases the load on your server."
msgstr "Het is een goed idee om niet een redirect voor pogingen tot brute kracht login pogingen in te stellen naar uw site, omdat het de belasting van uw server verhoogt."

#: admin/wp-security-brute-force-menu.php:420
msgid "Redirecting a hacker or malicious bot back to \"http://127.0.0.1\" is ideal because it deflects them back to their own local host and puts the load on their server instead of yours."
msgstr "Redirecting een hacker of kwaadaardige bot terug naar \"http://127.0.0.1\" is ideaal, omdat het hen terug stuurt naar hun eigen lokale host en de belasting op hun server plaatst in plaats van de jouwe."

#: admin/wp-security-brute-force-menu.php:427
msgid "My site has posts or pages which are password protected"
msgstr "Mijn site heeft berichten of pagina's die beschermd zijn met een wachtwoord"

#: admin/wp-security-brute-force-menu.php:430
msgid "Check this if you are using the native WordPress password protection feature for some or all of your blog posts or pages."
msgstr "Activeer dit als u gebruik maakt van de WordPress wachtwoordbeveiligingsfunctie voor sommige of alle van uw blog-berichten of pagina's."

#: admin/wp-security-brute-force-menu.php:435
msgid "In the cases where you are protecting some of your posts or pages using the in-built WordPress password protection feature, a few extra lines of directives and exceptions need to be added so that people trying to access pages are not automatically blocked."
msgstr ""

#: admin/wp-security-brute-force-menu.php:437
msgid "By enabling this checkbox, the plugin will add the necessary rules and exceptions so that people trying to access these pages are not automatically blocked."
msgstr ""

#: admin/wp-security-brute-force-menu.php:439
msgid "Helpful Tip:"
msgstr "Extra tip:"

#: admin/wp-security-brute-force-menu.php:441
msgid "If you do not use the WordPress password protection feature for your posts or pages then it is highly recommended that you leave this checkbox disabled."
msgstr "Als u geen gebruik maakt van de WordPress wachtwoordbeschermingsfunctie voor uw berichten of pagina's dan is het sterk aanbevolen dat u dit aankruisvak uitgeschakeld laat."

#: admin/wp-security-brute-force-menu.php:448
msgid "My site has a theme or plugins which use AJAX"
msgstr "Mijn site heeft een thema of plug-in die gebruik maakt van AJAX"

#: admin/wp-security-brute-force-menu.php:451
msgid "Check this if your site uses AJAX functionality."
msgstr "Kijk of jouw site AJAX gebruikt."

#: admin/wp-security-brute-force-menu.php:456
msgid "In the cases where your WordPress installation has a theme or plugin that uses AJAX, a few extra lines of directives and exceptions need to be added to prevent AJAX requests from being automatically blocked by the brute force prevention feature."
msgstr ""

#: admin/wp-security-brute-force-menu.php:458
msgid "By enabling this checkbox, the plugin will add the necessary rules and exceptions so that AJAX operations will work as expected."
msgstr ""

#: admin/wp-security-brute-force-menu.php:467
msgid "Save feature settings"
msgstr "Instellingen opslaan"

#: admin/wp-security-brute-force-menu.php:525
msgid "This feature allows you to add a CAPTCHA form on various WordPress login pages and forms."
msgstr "Deze eigenschap staat u toe om een CAPTCHA-formulier op diverse WordPress loginpagina's en formulieren toe te voegen."

#: admin/wp-security-brute-force-menu.php:526
msgid "Adding a CAPTCHA form on a login page or form is another effective yet simple \"Brute Force\" prevention technique."
msgstr "Het toevoegen van een CAPTCHA-formulier op een loginpagina of formulier is een andere effectieve maar eenvoudige \"Brute Force\" preventietechniek."

#: admin/wp-security-brute-force-menu.php:527
msgid "You have the option of using either %s or a plain maths CAPTCHA form."
msgstr "U hebt de mogelijkheid van het gebruik van ofwel %s of een gewone wiskunde-CAPTCHA vorm."

#: admin/wp-security-brute-force-menu.php:528
msgid "If you enable Google reCAPTCHA the reCAPTCHA widget will be displayed for all forms the CAPTCHA settings below."
msgstr "Wanneer u Google reCAPTCHA activeert zal de reCAPTCHA-widget worden weergegeven voor alle formulieren met de CAPTCHA-instellingen hieronder."

#: admin/wp-security-brute-force-menu.php:529
msgid "If Google reCAPTCHA is disabled the simple maths CAPTCHA form will apply and users will need to enter the answer to a simple mathematical question."
msgstr "Als Google reCAPTCHA is uitgeschakeld, is het eenvoudige wiskunde-captcha-formulier van toepassing en moeten gebruikers het antwoord op een eenvoudige wiskundige vraag invoeren."

#: admin/wp-security-brute-force-menu.php:535
msgid "Google reCAPTCHA settings"
msgstr "Google reCAPTCHA-instellingen"

#: admin/wp-security-brute-force-menu.php:540
msgid "By enabling these settings the Google reCAPTCHA v2 widget will be applied by default for all forms with CAPTCHA enabled."
msgstr ""

#: admin/wp-security-brute-force-menu.php:549
msgid "reCAPTCHA will not work because you have disabled login lockout by activating the AIOS_DISABLE_LOGIN_LOCKOUT constant value in a configuration file."
msgstr ""

#: admin/wp-security-brute-force-menu.php:550
msgid "To enable it, define AIOS_DISABLE_LOGIN_LOCKOUT constant value as false, or remove it."
msgstr ""

#: admin/wp-security-brute-force-menu.php:558
msgid "Use Google reCAPTCHA as default"
msgstr "Gebruik standaard Google reCAPTCHA"

#: admin/wp-security-brute-force-menu.php:561
msgid "Check this if you want to default to Google reCAPTCHA for all settings below. (If this is left unchecked, all CAPTCHA forms will revert to the plain maths CAPTCHA)"
msgstr "Markeer dit als u standaard Google reCAPTCHA voor alle instellingen hieronder wil gebruiken. (Als dit niet is aangevinkt, dan zullen alle captcha-formulieren terugkeren naar de gewone wiskundige-CAPTCHA)"

#: admin/wp-security-brute-force-menu.php:565
msgid "Site key"
msgstr "Site-sleutel"

#: admin/wp-security-brute-force-menu.php:571
msgid "Secret key"
msgstr "Geheime sleutel"

#: admin/wp-security-brute-force-menu.php:580
msgid "Login form CAPTCHA settings"
msgstr "Loginformulier Captcha-instellingen"

#: admin/wp-security-brute-force-menu.php:589
msgid "Enable CAPTCHA on login page"
msgstr "Captcha gebruiken op loginpagina"

#: admin/wp-security-brute-force-menu.php:592
msgid "Check this if you want to insert a CAPTCHA form on the login page."
msgstr "Vink dit aan als je een captcha wilt toevoegen aan de loginpagina"

#: admin/wp-security-brute-force-menu.php:598
msgid "Lost password form CAPTCHA settings"
msgstr "Wachtwoord vergeten Captcha-instellingen"

#: admin/wp-security-brute-force-menu.php:608
msgid "Enable CAPTCHA on lost password page"
msgstr "Captcha gebruiken op Wachtwoord-vergeten-pagina"

#: admin/wp-security-brute-force-menu.php:611
msgid "Check this if you want to insert a CAPTCHA form on the lost password page."
msgstr "Vink dit aan als je een captcha-formulier wilt toevoegen aan de wachtwoord-vergeten-pagina"

#: admin/wp-security-brute-force-menu.php:617
msgid "Custom login form CAPTCHA settings"
msgstr "Eigen loginformulier Captcha-instellingen"

#: admin/wp-security-brute-force-menu.php:626
msgid "Enable CAPTCHA on custom login form"
msgstr "Gebruik captcha op eigen loginformulieren"

#: admin/wp-security-brute-force-menu.php:629
msgid "Check this if you want to insert CAPTCHA on a custom login form generated by the following WP function: wp_login_form()"
msgstr "Vink dit aan als je een captcha wilt toevoegen aan een eigen loginformulier dat aangemaakt word met de volgende WP-functie: wp_login_form()"

#: admin/wp-security-brute-force-menu.php:639
msgid "WooCommerce forms CAPTCHA settings"
msgstr "Woocommerce Formulieren Captcha Instellingen"

#: admin/wp-security-brute-force-menu.php:648
msgid "Enable CAPTCHA on WooCommerce login form"
msgstr "Gebruik Captcha op Woocommerce Login pagina"

#: admin/wp-security-brute-force-menu.php:651
msgid "Check this if you want to insert CAPTCHA on a WooCommerce login form."
msgstr "Vink dit aan als je gebruik wilt maken van captcha op de Woocommerce login pagina"

#: admin/wp-security-brute-force-menu.php:661
msgid "Enable CAPTCHA on WooCommerce lost password form"
msgstr ""

#: admin/wp-security-brute-force-menu.php:664
msgid "Check this if you want to insert CAPTCHA on a WooCommerce lost password form."
msgstr ""

#: admin/wp-security-brute-force-menu.php:674
msgid "Enable CAPTCHA on WooCommerce registration form"
msgstr "Gebruik Captcha op Woocommerce Registratie pagina"

#: admin/wp-security-brute-force-menu.php:677
msgid "Check this if you want to insert CAPTCHA on a WooCommerce registration form."
msgstr "Vink dit aan als je gebruik wilt maken van captcha op de Woocommerce registratie pagina"

#: admin/wp-security-brute-force-menu.php:749
msgid "The All In One WP Security Whitelist feature gives you the option of only allowing certain IP addresses or ranges to have access to your WordPress login page."
msgstr "De All In One WP Security Whitelist optie geeft jou de mogelijkheid om alleen bepaalde IP-adressen of ranges toegang te verlenen aan jouw WordPress-loginpagina."

#: admin/wp-security-brute-force-menu.php:750
msgid "This feature will deny login access for all IP addresses which are not in your whitelist as configured in the settings below."
msgstr "Deze optie weigert toegang tot het loginscherm voor alle IP-adressen die niet hieronder ingevuld worden."

#: admin/wp-security-brute-force-menu.php:751
msgid "The plugin achieves this by writing the appropriate directives to your .htaccess file."
msgstr "De plugin doet dit door de juiste regels toe te voegen aan jouw .htaccess-bestand."

#: admin/wp-security-brute-force-menu.php:752
msgid "By allowing/blocking IP addresses, you are using the most secure first line of defence because login access will only be granted to whitelisted IP addresses and other addresses will be blocked as soon as they try to access your login page."
msgstr "Door IP-adressen toe te staan of te blokkeren via het .htaccess-bestand maak je gebruik van de beste beschermingsmogelijkheid omdat inloggen alleen toegestaan is voor toegestane IP-adressen en andere adressen geblokkeerd worden zodra ze jouw loginpagina proberen te bereiken."

#: admin/wp-security-brute-force-menu.php:760
msgid "Attention: If in addition to enabling the white list feature, you also have one of the %s or %s features enabled, <strong>you will still need to use your secret word or special slug in the URL when trying to access your WordPress login page</strong>."
msgstr "Attentie: Als je naast het gebruiken van de white-list optie je ook %s of %s gebruikt, <strong>zal je nog steeds je geheime woord of eigen slug moeten gebruiken om je WordPress inlogpagina te bezoeken</strong>."

#: admin/wp-security-brute-force-menu.php:761
msgid "These features are NOT functionally related. Having both of them enabled on your site means you are creating 2 layers of security."
msgstr "Deze opties zijn NIET hetzelfde. Als je beide gebruikt betekent het dat je een extra beveiligingslaag toevoegt."

#: admin/wp-security-brute-force-menu.php:772
msgid "Login IP whitelist settings"
msgstr "IP-login Whitelist-instellingen"

#: admin/wp-security-brute-force-menu.php:783
msgid "Enable IP whitelisting"
msgstr "IP Whitelist gebruiken"

#: admin/wp-security-brute-force-menu.php:786
#: admin/wp-security-user-login-menu.php:408
msgid "Check this if you want to enable the whitelisting of selected IP addresses specified in the settings below"
msgstr "Vink dit aan als je de hieronder aangegeven IP-adressen wilt whitelisten"

#: admin/wp-security-brute-force-menu.php:790
msgid "Your current IP address"
msgstr "Jouw huidige IP-adres"

#: admin/wp-security-brute-force-menu.php:793
msgid "You can copy and paste this address in the text box below if you want to include it in your login whitelist."
msgstr "Je kan dit kopiëren en plakken in het veld hier onder als je dit adres wilt whitelisten."

#: admin/wp-security-brute-force-menu.php:797
#: admin/wp-security-user-login-menu.php:412
msgid "Enter whitelisted IP addresses:"
msgstr "Vul Whitelisted IP-adres in:"

#: admin/wp-security-brute-force-menu.php:801
#: admin/wp-security-user-login-menu.php:416
msgid "Enter one or more IP addresses or IP ranges you wish to include in your whitelist."
msgstr ""

#: admin/wp-security-brute-force-menu.php:801
msgid "Only the addresses specified here will have access to the WordPress login page."
msgstr ""

#: admin/wp-security-brute-force-menu.php:839
msgid "This feature allows you to add a special hidden \"honeypot\" field on the WordPress login page. This will only be visible to robots and not humans."
msgstr "Deze optie voegt een \"honeypot\"-veld toe aan het WordPress-loginveld. Dit is alleen zichtbaar voor robots en niet voor mensen."

#: admin/wp-security-brute-force-menu.php:840
msgid "Since robots usually fill in every input field from a login form, they will also submit a value for the special hidden honeypot field."
msgstr "Omdat robots meestal elk veld in een formulier invullen zullen ze ook het verborgen honeypot-veld invullen."

#: admin/wp-security-brute-force-menu.php:841
#: admin/wp-security-user-registration-menu.php:278
msgid "The way honeypots work is that a hidden field is placed somewhere inside a form which only robots will submit. If that field contains a value when the form is submitted then a robot has most likely submitted the form and it is consequently dealt with."
msgstr "Een honeypot is een verbogen veld dat ergens in een formulier word geplaatst en dat alleen een robot zal invullen. Als het veld is ingevuld dan heeft waarschijnlijk een robot dit formulier ingevuld en zal daar naar gehandeld worden."

#: admin/wp-security-brute-force-menu.php:842
msgid "Therefore, if the plugin detects that this field has a value when the login form is submitted, then the robot which is attempting to login to your site will be redirected to its localhost address - http://127.0.0.1."
msgstr "Dus, als de plugin merkt dat dit veld is ingevuld zal de robot doorverwezen worden naar zijn localhost adres - http://127.0.0.1."

#: admin/wp-security-brute-force-menu.php:848
msgid "Login form honeypot settings"
msgstr "Login-honeypot-instellingen"

#: admin/wp-security-brute-force-menu.php:859
msgid "Enable honeypot on login page"
msgstr "Honeypot-gebruik op de loginpagina"

#: admin/wp-security-brute-force-menu.php:862
msgid "Check this if you want to enable the honeypot feature for the login page"
msgstr "Vink dit aan als je gebruik wilt maken van de honeypot op de loginpagina"

#: admin/wp-security-dashboard-menu.php:27
#: admin/wp-security-dashboard-menu.php:374
#: classes/wp-security-user-login.php:74
msgid "Locked IP addresses"
msgstr "Geblokkeerde IP-adressen"

#: admin/wp-security-dashboard-menu.php:28
msgid "Permanent block list"
msgstr "Permanente blokkeerlijst"

#: admin/wp-security-dashboard-menu.php:29
msgid "Logs"
msgstr ""

#: admin/wp-security-dashboard-menu.php:33
msgid "Premium upgrade"
msgstr ""

#: admin/wp-security-dashboard-menu.php:131
#: admin/wp-security-dashboard-menu.php:518
#: admin/wp-security-user-login-menu.php:53
#: classes/grade-system/wp-security-feature-item-manager.php:49
msgid "Login lockout"
msgstr ""

#: admin/wp-security-dashboard-menu.php:132
msgid "This tab displays the list of all IP addresses which are currently temporarily locked out due to the login lockout feature:"
msgstr ""

#: admin/wp-security-dashboard-menu.php:138
msgid "Currently locked out IP addresses and ranges"
msgstr "Momenteel vergrendelde IP-adressen en bereiken"

#: admin/wp-security-dashboard-menu.php:183
msgid "This tab displays the list of all permanently blocked IP addresses."
msgstr "Dit tabblad toont de lijst met alle permanent geblokkeerde IP-adressen."

#: admin/wp-security-dashboard-menu.php:184
#: admin/wp-security-spam-menu.php:339
msgid "NOTE: This feature does NOT use the .htaccess file to permanently block the IP addresses so it should be compatible with all web servers running WordPress."
msgstr "OPMERKING: deze functie maakt GEEN gebruik van het .htaccess-bestand om de IP-adressen permanent te blokkeren, zodat het compatibel moet zijn met alle webservers waarop WordPress wordt uitgevoerd."

#: admin/wp-security-dashboard-menu.php:189
msgid "Permanently blocked IP addresses"
msgstr "Permanent geblokkeerde IP-adressen"

#: admin/wp-security-dashboard-menu.php:200
#: admin/wp-security-firewall-menu.php:1151
#: admin/wp-security-user-login-menu.php:485
#: admin/wp-security-user-login-menu.php:643
#: admin/wp-security-user-registration-menu.php:164
msgid "Search"
msgstr ""

#: admin/wp-security-dashboard-menu.php:238
#: admin/wp-security-dashboard-menu.php:249
#: admin/wp-security-dashboard-menu.php:260
msgid "All In One WP Security & Firewall"
msgstr ""

#: admin/wp-security-dashboard-menu.php:250
msgid "Debug logs have been cleared."
msgstr ""

#: admin/wp-security-dashboard-menu.php:261
msgid "Unable to clear the logs; an invalid nonce was provided"
msgstr ""

#: admin/wp-security-dashboard-menu.php:274
msgid "Debug log options"
msgstr ""

#: admin/wp-security-dashboard-menu.php:281
msgid "Clear logs"
msgstr ""

#: admin/wp-security-dashboard-menu.php:289
msgid "Debug logs"
msgstr ""

#: admin/wp-security-dashboard-menu.php:362
msgid "Security strength meter"
msgstr "Veiligheidssterktemeter"

#: admin/wp-security-dashboard-menu.php:363
msgid "Security points breakdown"
msgstr "Beveiliging punten breakdown"

#: admin/wp-security-dashboard-menu.php:364
msgid "Spread the word"
msgstr "Verspreid het woord"

#: admin/wp-security-dashboard-menu.php:365
msgid "Get to know the developers"
msgstr "Maak kennis met de ontwikkelaars"

#: admin/wp-security-dashboard-menu.php:366
msgid "Critical feature status"
msgstr "Status belangrijkste opties"

#: admin/wp-security-dashboard-menu.php:367
msgid "Last 5 logins"
msgstr "Laatste 5 logins"

#: admin/wp-security-dashboard-menu.php:368
msgid "Maintenance mode status"
msgstr "Status Onderhoudmodus"

#: admin/wp-security-dashboard-menu.php:373
#: admin/wp-security-dashboard-menu.php:664
#: admin/wp-security-user-login-menu.php:57
msgid "Logged in users"
msgstr "Ingelogde gebruikers"

#: admin/wp-security-dashboard-menu.php:417
msgid "Total Achievable Points: "
msgstr "Totaal te behalen punten: "

#: admin/wp-security-dashboard-menu.php:419
msgid "Current Score of Your Site: "
msgstr "Huide site-score: "

#: admin/wp-security-dashboard-menu.php:472
msgid "We are working hard to make your WordPress site more secure. Please support us, here is how:"
msgstr "Wij doen er alles aan jouw WordPress-site veiliger te maken. Help ons, hier staat hoe:"

#: admin/wp-security-dashboard-menu.php:473
msgid "Follow us on"
msgstr ""

#: admin/wp-security-dashboard-menu.php:477
msgid "Post to Twitter"
msgstr ""

#: admin/wp-security-dashboard-menu.php:481
msgid "Give us a good rating"
msgstr ""

#: admin/wp-security-dashboard-menu.php:488
msgid "Wanna know more about the developers behind this plugin?"
msgstr "Wil je meer weten over de ontwikkelaars achter deze plug-in ?"

#: admin/wp-security-dashboard-menu.php:499
msgid "Below is the current status of the critical features that you should activate on your site to achieve a minimum level of recommended security"
msgstr "Hieronder staat de status van de belangrijkste opties voor het behalen van een minimaal beveiligingsniveau"

#: admin/wp-security-dashboard-menu.php:503
msgid "Admin username"
msgstr "Admin-gebruikersnaam"

#: admin/wp-security-dashboard-menu.php:533
msgid "File permission"
msgstr "Bestandstoegang"

#: admin/wp-security-dashboard-menu.php:548
msgid "Basic firewall"
msgstr "Standaard firewall"

#: admin/wp-security-dashboard-menu.php:577
msgid "No data found."
msgstr "Geen gegevens gevonden!"

#: admin/wp-security-dashboard-menu.php:581
msgid "Last 5 logins summary:"
msgstr "Samenvatting laatste 5 logins:"

#: admin/wp-security-dashboard-menu.php:585
msgid "User"
msgstr "Gebruiker"

#: admin/wp-security-dashboard-menu.php:586
#: admin/wp-security-list-404.php:95
#: admin/wp-security-list-login-fails.php:56
#: admin/wp-security-list-permanent-blocked-ip.php:68
msgid "Date"
msgstr "Datum"

#: admin/wp-security-dashboard-menu.php:587
msgid "IP"
msgstr "IP"

#: admin/wp-security-dashboard-menu.php:608
msgid "Maintenance mode is currently enabled. Remember to turn it off when you are done"
msgstr "Onderhoudmodus is momenteel actief. Vergeet dit niet uit te zetten als je klaar bent"

#: admin/wp-security-dashboard-menu.php:610
msgid "Maintenance mode is currently off."
msgstr "Onderhoudmodus staat momenteel uit."

#: admin/wp-security-dashboard-menu.php:614
msgid "Maintenance mode"
msgstr "Onderhoudmodus"

#: admin/wp-security-dashboard-menu.php:632
msgid "Cookie based brute force"
msgstr ""

#: admin/wp-security-dashboard-menu.php:636
#: admin/wp-security-dashboard-menu.php:654
msgid "The %s feature is currently active."
msgstr "De %s optie is momenteel actief."

#: admin/wp-security-dashboard-menu.php:637
#: admin/wp-security-dashboard-menu.php:655
msgid "Your new WordPress login URL is now:"
msgstr "Je nieuwe WordPress inlog-URL is:"

#: admin/wp-security-dashboard-menu.php:666
msgid "Number of users currently logged into your site (including you) is:"
msgstr "Aantal gebruikers ingelogd op jouw site (inclusief jijzelf):"

#: admin/wp-security-dashboard-menu.php:667
msgid "There are no other users currently logged in."
msgstr "Er zijn momenteel geen gebruikers ingelogd."

#: admin/wp-security-dashboard-menu.php:680
msgid "Number of users currently logged in site-wide (including you) is:"
msgstr ""

#: admin/wp-security-dashboard-menu.php:681
msgid "There are no other site-wide users currently logged in."
msgstr "Er zijn geen gebruikers momenteel ingelogd."

#: admin/wp-security-dashboard-menu.php:694
#: admin/wp-security-dashboard-menu.php:711
msgid "Go to the %s menu to see more details"
msgstr "Ga naar het %s menu voor meer details"

#: admin/wp-security-dashboard-menu.php:707
msgid "There are no IP addresses currently locked out."
msgstr "Er zijn momenteel geen IP-adressen geblokkeerd."

#: admin/wp-security-dashboard-menu.php:710
msgid "Number of temporarily locked out IP addresses: "
msgstr "Aantal tijdelijk geblokkeerde IP-adressen: "

#: admin/wp-security-database-menu.php:52
msgid "UpdraftPlus is installed but currently not active."
msgstr ""

#: admin/wp-security-database-menu.php:52
msgid "Follow this link to activate UpdraftPlus, to take a backup."
msgstr ""

#: admin/wp-security-database-menu.php:57
msgid "Follow this link to install UpdraftPlus, to take a database backup."
msgstr ""

#: admin/wp-security-database-menu.php:87
#: admin/wp-security-database-menu.php:92
msgid "Database backup"
msgstr "DB back-up"

#: admin/wp-security-database-menu.php:91
#: classes/grade-system/wp-security-feature-item-manager.php:65
msgid "Database prefix"
msgstr "DB-prefix"

#: admin/wp-security-database-menu.php:119
msgid "Database security"
msgstr "Databasebeveiliging"

#: admin/wp-security-database-menu.php:147
msgid "Nonce check failed for DB prefix change operation!"
msgstr "Nonce check mislukt voor het veranderen van de DB-prefix!"

#: admin/wp-security-database-menu.php:155
msgid "The plugin has detected that it cannot write to the wp-config.php file. This feature can only be used if the plugin can successfully write to the wp-config.php file."
msgstr "De plugin heeft ontdekt dat het niet kan schrijven naar het wp-config. php-bestand. Deze functie kan alleen worden gebruikt als de plugin met succes kan schrijven naar het wp-config. php-bestand."

#: admin/wp-security-database-menu.php:168
msgid "Please enter a value for the DB prefix."
msgstr "Vul een waarde in voor de DB-prefix."

#: admin/wp-security-database-menu.php:177
msgid "<strong>ERROR</strong>: The table prefix can only contain numbers, letters, and underscores."
msgstr "<strong>FOUT</strong>: het tabel voorvoegsel kan alleen cijfers, letters en underscores bevatten."

#: admin/wp-security-database-menu.php:186
#: admin/wp-security-database-menu.php:245
msgid "Change database prefix"
msgstr "Verander database-prefix"

#: admin/wp-security-database-menu.php:189
msgid "Your WordPress database is the most important asset of your website because it contains a lot of your site's precious information."
msgstr "Uw WordPress-DB is de belangrijkste troef van uw website, omdat deze heel veel kostbare informatie van uw site bevat."

#: admin/wp-security-database-menu.php:190
msgid "The database is also a target for hackers via methods such as SQL injections and malicious and automated code which targets certain tables."
msgstr "De DB is ook een doelwit voor hackers via methoden zoals SQL-injecties en kwaadaardige en geautomatiseerde code die zich op bepaalde tabellen richt."

#: admin/wp-security-database-menu.php:191
msgid "One way to add a layer of protection for your DB is to change the default WordPress table prefix from \"wp_\" to something else which will be difficult for hackers to guess."
msgstr "Een manier om een laag van bescherming voor uw database toe te voegen is om de standaard WordPress tabelprefix te veranderen van \"wp_\" in iets dat moeilijk door hackers te raden is."

#: admin/wp-security-database-menu.php:192
msgid "This feature allows you to easily change the prefix to a value of your choice or to a random value set by this plugin."
msgstr "Met deze functie kunt u de prefixgemakkelijk veranderen naar een waarde van uw keuze of naar een willekeurige waarde die deze plugin voor u in kan stellen."

#: admin/wp-security-database-menu.php:198
msgid "Database prefix options"
msgstr "Opties database-prefix"

#: admin/wp-security-database-menu.php:210
msgid "database backup"
msgstr "DB back-up"

#: admin/wp-security-database-menu.php:211
msgid "It is recommended that you perform a %s before using this feature"
msgstr "Het wordt aanbevolen dat u een %s uitvoert voordat u deze functie gebruikt"

#: admin/wp-security-database-menu.php:221
msgid "Current database table prefix"
msgstr "Huidige database-prefix"

#: admin/wp-security-database-menu.php:227
msgid "Your site is currently using the default WordPress database prefix value of \"wp_\"."
msgstr ""

#: admin/wp-security-database-menu.php:227
msgid "To increase your site's security you should consider changing the database prefix value to another value."
msgstr ""

#: admin/wp-security-database-menu.php:234
msgid "Generate new database table prefix"
msgstr "Nieuwe database-prefix aanmaken"

#: admin/wp-security-database-menu.php:238
msgid "Check this if you want the plugin to generate a random 6 character string for the table prefix"
msgstr "Activeer dit als u wilt dat de plug-in een willekeurige tekenreeks van 6 karakters voor de tabel-prefix genereert"

#: admin/wp-security-database-menu.php:239
msgid "OR"
msgstr "OF"

#: admin/wp-security-database-menu.php:241
msgid "Choose your own database prefix by specifying a string which contains letters and/or numbers and/or underscores. Example: xyz_"
msgstr ""

#: admin/wp-security-database-menu.php:265
msgid "Take a database backup using UpdraftPlus"
msgstr ""

#: admin/wp-security-database-menu.php:270
msgid "Manual backup"
msgstr "Handmatige back-up"

#: admin/wp-security-database-menu.php:274
msgid "UpdraftPlus Backup/Restore"
msgstr ""

#: admin/wp-security-database-menu.php:274
msgid "Your backups are on the UpdraftPlus Backup/Restore admin page."
msgstr ""

#: admin/wp-security-database-menu.php:276
msgid "Create database backup now"
msgstr ""

#: admin/wp-security-database-menu.php:308
msgid "Error - Could not get tables or no tables found!"
msgstr "Error - Kon geen tabellen ophalen of vinden!"

#: admin/wp-security-database-menu.php:312
msgid "Starting DB prefix change operations....."
msgstr "Beginnen met het veranderen van het DB-prefix....."

#: admin/wp-security-database-menu.php:314
msgid "Your WordPress system has a total of %s tables and your new DB prefix will be: %s"
msgstr "Jouw WordPress-systeem heeft %s tabellen en jouw nieuwe DB-prefix wordt: %s"

#: admin/wp-security-database-menu.php:320
#: classes/wp-security-utility.php:306
msgid "Failed to make a backup of the wp-config.php file. This operation will not go ahead."
msgstr "Het maken van een back-up van het wp-config. php-bestand is mislukt. Deze operatie zal niet verder gaan."

#: admin/wp-security-database-menu.php:324
msgid "A backup copy of your wp-config.php file was created successfully!"
msgstr "Een back-up van uw wp-config. php-bestand is succesvol aangemaakt!"

#: admin/wp-security-database-menu.php:351
msgid "%s table name update failed"
msgstr "%s tabelnaam bijwerken is mislukt"

#: admin/wp-security-database-menu.php:363
msgid "Please change the prefix manually for the above tables to: %s"
msgstr "Wijzig het voorvoegsel handmatig voor de bovenstaande tabellen naar: %s"

#: admin/wp-security-database-menu.php:366
msgid "%s tables had their prefix updated successfully!"
msgstr "van %s tabellen is de prefix succesvol bijgewerkt!"

#: admin/wp-security-database-menu.php:387
msgid "wp-config.php file was updated successfully!"
msgstr "wp-config.php is succesvol bijgewerkt!"

#: admin/wp-security-database-menu.php:390
msgid "The \"wp-config.php\" file was not able to be modified."
msgstr ""

#: admin/wp-security-database-menu.php:390
msgid "Please modify this file manually using your favourite editor and search for variable \"$table_prefix\" and assign the following value to that variable: %s"
msgstr ""

#: admin/wp-security-database-menu.php:401
#: admin/wp-security-database-menu.php:420
msgid "Update of table %s failed: unable to change %s to %s"
msgstr "Update van tabel %s is mislukt: kan %s niet wijzigen in %s"

#: admin/wp-security-database-menu.php:405
msgid "The options table records which had references to the old DB prefix were updated successfully!"
msgstr "De records van de optiestabel die verwijzingen had naar de oude DB-prefix werden succesvol bijgewerkt!"

#: admin/wp-security-database-menu.php:424
msgid "The %s table records which had references to the old DB prefix were updated successfully!"
msgstr "De %s tabel records met verwijzingen naar de oude DB-prefix werden succesvol bijgewerkt!"

#: admin/wp-security-database-menu.php:452
msgid "Error updating user_meta table where new meta_key = %s, old meta_key = %s and user_id = %s."
msgstr "Fout bij het bijwerken van de user_meta tabel waar nieuwe meta_key = %s, oude meta_key = %s en user_id = %s."

#: admin/wp-security-database-menu.php:457
msgid "The usermeta table records which had references to the old DB prefix were updated successfully!"
msgstr "De usermeta tabel-records die verwijzingen naar de oude DB-prefix hadden werden succesvol bijgewerkt!"

#: admin/wp-security-database-menu.php:459
msgid "The database prefix change tasks have been completed."
msgstr "Het veranderen van de DB-prefix is afgerond."

#: admin/wp-security-database-menu.php:503
msgid "Checking for MySQL tables of type \"view\"....."
msgstr "Controleren op MySQL-tabellen van het type \" view \" ....."

#: admin/wp-security-database-menu.php:520
msgid "Update of the following MySQL view definition failed: %s"
msgstr "Actualisering van de volgende MySQL-view-definitie mislukt: %s"

#: admin/wp-security-database-menu.php:527
msgid "%s view definitions were updated successfully!"
msgstr "%s view definities zijn bijgewerkt!"

#: admin/wp-security-filescan-menu.php:26
#: classes/grade-system/wp-security-feature-item-manager.php:127
msgid "File change detection"
msgstr "Bestandwijzigingen"

#: admin/wp-security-filescan-menu.php:27
msgid "Malware scan"
msgstr "Malware-scan"

#: admin/wp-security-filescan-menu.php:88
msgid "There have been no file changes since the last scan."
msgstr "Er zijn geen wijzigingen in het bestand sinds de laatste scan."

#: admin/wp-security-filescan-menu.php:98
msgid "Nonce check failed for manual file change detection scan operation!"
msgstr "Nonce controle is mislukt voor de handmatige wijzigingsdetectie van de bestanden!"

#: admin/wp-security-filescan-menu.php:104
msgid "There was an error during the file change detection scan. Please check the AIOS logs."
msgstr ""

#: admin/wp-security-filescan-menu.php:110
msgid "The plugin has detected that this is your first file change detection scan. The file details from this scan will be used to detect file changes for future scans."
msgstr "De plugin heeft ontdekt dat dit uw eerste bestandswijzigingdetectie scan is. De bestandsdetails van deze scan zullen worden gebruikt om veranderingen op te sporen voor toekomstige scans!"

#: admin/wp-security-filescan-menu.php:112
msgid "Scan complete - There were no file changes detected!"
msgstr "Scan voltooid - er zijn geen wijzigingen in het bestand gedetecteerd!"

#: admin/wp-security-filescan-menu.php:133
msgid "You entered a non numeric value for the \"backup time interval\" field. It has been set to the default value."
msgstr "U hebt een niet-numerieke waarde voor het veld \"back-uptijdinterval\" ingevoerd. Het is nu ingesteld op de standaardwaarde."

#: admin/wp-security-filescan-menu.php:167
msgid "The following address was removed because it is not a valid email address: "
msgstr "Het volgende adres is verwijderd omdat het geen geldig e-mailadres is: "

#: admin/wp-security-filescan-menu.php:206
msgid "NEW SCAN COMPLETED: The plugin has detected that you have made changes to the \"File Types To Ignore\" or \"Files To Ignore\" fields."
msgstr ""

#: admin/wp-security-filescan-menu.php:206
msgid "In order to ensure that future scan results are accurate, the old scan data has been refreshed."
msgstr ""

#: admin/wp-security-filescan-menu.php:215
msgid "All In One WP Security & Firewall has detected that there was a change in your host's files."
msgstr "All In One WP Security & Firewall heeft ontdekt dat er een verandering was in de bestanden van uw host."

#: admin/wp-security-filescan-menu.php:217
msgid "View scan details and clear this message"
msgstr ""

#: admin/wp-security-filescan-menu.php:226
msgid "If given an opportunity hackers can insert their code or files into your system which they can then use to carry out malicious acts on your site."
msgstr "Als hackers een kans gegeven wordt dan kunnen zij hun code invoegen of bestanden op uw systeem plaatsen, die ze vervolgens kunnen gebruiken voor het uitvoeren van kwaadaardige handelingen op uw site."

#: admin/wp-security-filescan-menu.php:227
msgid "Being informed of any changes in your files can be a good way to quickly prevent a hacker from causing damage to your website."
msgstr "Op de hoogte gehouden worden van eventuele wijzigingen in uw bestanden kan een goede manier zijn om snel te voorkomen dat een hacker schade aan uw website veroorzaakt."

#: admin/wp-security-filescan-menu.php:228
msgid "In general, WordPress core and plugin files and file types such as \".php\" or \".js\" should not change often and when they do, it is important that you are made aware when a change occurs and which file was affected."
msgstr "In het algemeen zullen, WordPress core en plugin bestanden en bestandstypen, zoals \". php\" of \". js\" niet vaak veranderen, en wanneer ze dat doen is het belangrijk dat u bewust wordt gemaakt wanneer er een verandering optreedt en welk bestand werd beïnvloed."

#: admin/wp-security-filescan-menu.php:229
msgid "The \"File Change Detection Feature\" will notify you of any file change which occurs on your system, including the addition and deletion of files by performing a regular automated or manual scan of your system's files."
msgstr "De \"file change detection functie\" zal u op de hoogte brengen van een bestandswijziging die optreedt op uw systeem, met inbegrip van de toevoeging en verwijdering van bestanden door het uitvoeren van een regelmatige geautomatiseerde of handmatige scan van uw systeembestanden."

#: admin/wp-security-filescan-menu.php:230
msgid "This feature also allows you to exclude certain files or folders from the scan in cases where you know that they change often as part of their normal operation. (For example log files and certain caching plugin files may change often and hence you may choose to exclude such files from the file change detection scan)"
msgstr "Deze eigenschap staat u toe ook om bepaalde files of mappen van de controle uit te sluiten in gevallen waarvan u weet dat ze vaak als deel van hun normale verrichting veranderen. (Bijvoorbeeld log-bestanden en bepaalde caching plugin-bestanden kunnen vaak veranderen en dus u kunt ervoor kiezen om dergelijke bestanden uit te sluiten van de scan voor bestandswijziging)"

#: admin/wp-security-filescan-menu.php:241
msgid "It appears that your server is using an old PHP version which is missing the %s. The file scanner feature needs this class in order to work. If you would like to use this feature please upgrade your server PHP version to 5.3 or greater."
msgstr "Het blijkt dat uw server een oude PHP-versie gebruikt die %s mist. De functie bestandsscanner heeft deze klasse nodig om te kunnen werken. Als u deze eigenschap zou willen gebruiken gelieve de PHP-versie van uw server te upgraden naar versie 5.3 of hoger."

#: admin/wp-security-filescan-menu.php:249
msgid "Manual file change detection scan"
msgstr "Handmatige scan van bestandswijzigingen"

#: admin/wp-security-filescan-menu.php:255
msgid "To perform a manual file change detection scan click on the button below."
msgstr "Voor het uitvoeren van een handmatige scan op bestandswijzigingen, klik op de knop hieronder."

#: admin/wp-security-filescan-menu.php:258
msgid "Perform scan now"
msgstr "Nu scannen"

#: admin/wp-security-filescan-menu.php:262
msgid "View last saved file change results"
msgstr "Laatst opgeslagen resultaten van bestandswijziging weergeven"

#: admin/wp-security-filescan-menu.php:268
msgid "Click the button below to view the saved file change results from the last scan."
msgstr "Klik op de knop hieronder om de opgeslagen resulaten van de scan op bestandwijziging te bekijken."

#: admin/wp-security-filescan-menu.php:271
msgid "View last file change"
msgstr "Laatste bestandswijziging bekijken"

#: admin/wp-security-filescan-menu.php:275
msgid "File change detection settings"
msgstr "Instellingen voor detectie van bestandwijziging"

#: admin/wp-security-filescan-menu.php:287
msgid "Enable automated file change detection scan"
msgstr "Automatische detectie van bestandswijzigingen inschakelen"

#: admin/wp-security-filescan-menu.php:290
msgid "Check this if you want the system to automatically/periodically scan your files to check for file changes based on the settings below"
msgstr "Activeer dit als u wilt dat het systeem automatisch/periodiek uw bestanden scant en controleert op veranderingen op basis van de onderstaande instellingen"

#: admin/wp-security-filescan-menu.php:294
msgid "Scan time interval"
msgstr "Scan tijdinterval"

#: admin/wp-security-filescan-menu.php:297
msgid "Hours"
msgstr "Uren"

#: admin/wp-security-filescan-menu.php:298
msgid "Days"
msgstr "Dagen"

#: admin/wp-security-filescan-menu.php:299
msgid "Weeks"
msgstr "Weken"

#: admin/wp-security-filescan-menu.php:301
msgid "Set the value for how often you would like a scan to occur"
msgstr "Hoe vaak wilt u dat er een scan gedaan wordt"

#: admin/wp-security-filescan-menu.php:305
msgid "File types to ignore"
msgstr "Te negeren bestandstypen"

#: admin/wp-security-filescan-menu.php:308
msgid "Enter each file type or extension on a new line which you wish to exclude from the file change detection scan."
msgstr "Voer elk bestandstype of extensie op een nieuwe regel die u wilt uitsluiten van de scan op bestandswijziging."

#: admin/wp-security-filescan-menu.php:312
msgid "You can exclude file types from the scan which would not normally pose any security threat if they were changed. These can include things such as image files."
msgstr "U kunt bestandstypen uitsluiten van de scan die normaalgesproken geen bedreiging vormen voor de beveiliging als deze zijn gewijzigd. Dit kunnen dingen zijn zoals bestanden met afbeeldingen."

#: admin/wp-security-filescan-menu.php:313
msgid "Example: If you want the scanner to ignore files of type jpg, png, and bmp, then you would enter the following:"
msgstr "Voorbeeld: als u wilt dat de scanner bestanden van het type jpg, png, en bmp negeert, dan zou je het volgende in kunnen voeren:"

#: admin/wp-security-filescan-menu.php:314
msgid "jpg"
msgstr "jpg"

#: admin/wp-security-filescan-menu.php:315
msgid "png"
msgstr "png"

#: admin/wp-security-filescan-menu.php:316
msgid "bmp"
msgstr "bmp"

#: admin/wp-security-filescan-menu.php:322
msgid "Files/Directories to ignore"
msgstr "Bestanden/Mappen uitsluiten"

#: admin/wp-security-filescan-menu.php:325
msgid "Enter each file or directory on a new line which you wish to exclude from the file change detection scan."
msgstr "Voer elk bestand of map op een nieuwe regel in die u wilt uitsluiten van de scan voor bestandswijziging."

#: admin/wp-security-filescan-menu.php:329
msgid "You can exclude specific files/directories from the scan which would not normally pose any security threat if they were changed. These can include things such as log files."
msgstr "U kunt specifieke bestanden/directories uitsluiten van de scan die normaalgesproken geen bedreiging vormen voor de veiligheid als ze werden veranderd. Deze kunnen zaken zoals logboeken omvatten."

#: admin/wp-security-filescan-menu.php:330
msgid "Example: If you want the scanner to ignore certain files in different directories or whole directories, then you would enter the following:"
msgstr "Voorbeeld: als u wilt dat de scanner bepaalde bestanden in verschillende mappen of hele mappen negeert, voert u het volgende in:"

#: admin/wp-security-filescan-menu.php:331
msgid "cache/config/master.php"
msgstr "cache/config/master.php"

#: admin/wp-security-filescan-menu.php:332
msgid "somedirectory"
msgstr "eenmap"

#: admin/wp-security-filescan-menu.php:339
msgid "Send email when change detected"
msgstr "Verstuur e-mail als er een wijziging is vastgesteld"

#: admin/wp-security-filescan-menu.php:343
msgid "Check this if you want the system to email you if a file change was detected"
msgstr "Vink dit aan als je een e-mail wilt ontvangen als een bestand is veranderd"

#: admin/wp-security-filescan-menu.php:347
msgid "Enter one or more email addresses on a new line."
msgstr "Voer een of meer e-mailadressen in op een nieuwe regel."

#: admin/wp-security-filescan-menu.php:364
msgid "What is malware?"
msgstr "Wat is malware?"

#: admin/wp-security-filescan-menu.php:365
msgid "The word malware stands for Malicious Software. It can consist of things like trojan horses, adware, worms, spyware and any other undesirable code which a hacker will try to inject into your website."
msgstr "Het woord malware staat voor kwaadaardige software. Het kan bestaan uit dingen zoals Trojaanse paarden, adware, wormen, spyware en andere ongewenste code die een hacker zal proberen te injecteren in uw website."

#: admin/wp-security-filescan-menu.php:366
msgid "Often when malware code has been inserted into your site you will normally not notice anything out of the ordinary based on appearances, but it can have a dramatic effect on your site's search ranking."
msgstr "Vaak wanneer malware-code is ingevoegd in uw site zult u normaalgesproken niets vreemds merken in de praktijk, maar het kan een dramatisch effect hebben op de ranking van uw site."

#: admin/wp-security-filescan-menu.php:367
msgid "This is because the bots and spiders from search engines such as Google have the capability to detect malware when they are indexing the pages on your site, and consequently they can blacklist your website which will in turn affect your search rankings."
msgstr "Dit komt omdat de bots en spiders van zoekmachines zoals Google de mogelijkheid hebben om malware te detecteren wanneer zij de indexering van de pagina's op uw site uitvoeren, en dus kunnen ze uw website plaatsen op de zwarte lijst die op zijn beurt invloed kan hebben op de ranking van uw site."

#: admin/wp-security-filescan-menu.php:369
msgid "CLICK HERE"
msgstr ""

#: admin/wp-security-filescan-menu.php:371
msgid "Scanning for malware"
msgstr "Aan het scannen naar malware"

#: admin/wp-security-filescan-menu.php:372
msgid "Due to the constantly changing and complex nature of Malware, scanning for such things using a standalone plugin will not work reliably. This is something best done via an external scan of your site regularly."
msgstr "Vanwege de voortdurend veranderende en complexe aard van malware, zal scannen voor zulke dingen met behulp van een standalone plugin niet betrouwbaar werken. Dit is iets dat het beste gedaan kan worden via een regelmatige externe scan van uw site."

#: admin/wp-security-filescan-menu.php:373
msgid "This is why we have created an easy-to-use scanning service which is hosted off our own server which will scan your site for malware once every day and notify you if it finds anything."
msgstr "Dit is waarom we een eenvoudig te gebruiken scanservice hebben gemaakt, die wordt gehost vanaf onze eigen server die uw site een keer per dag scant op malware en u op de hoogte brengt als het iets vindt."

#: admin/wp-security-filescan-menu.php:374
msgid "When you sign up for this service you will get the following:"
msgstr "Wanneer u zich aanmeldt voor deze dienst krijgt u het volgende:"

#: admin/wp-security-filescan-menu.php:376
msgid "Automatic daily scan of 1 website"
msgstr "Automatische dagelijkse scan van 1 website"

#: admin/wp-security-filescan-menu.php:377
msgid "Automatic malware and blacklist monitoring"
msgstr ""

#: admin/wp-security-filescan-menu.php:378
msgid "Automatic email alerting"
msgstr "Automatische e-mailmeldingen"

#: admin/wp-security-filescan-menu.php:379
msgid "Site uptime monitoring"
msgstr "Site uptime monitoring"

#: admin/wp-security-filescan-menu.php:380
msgid "Site response time monitoring"
msgstr "Monitoring site-responsetijd"

#: admin/wp-security-filescan-menu.php:381
msgid "We provide advice for malware cleanup"
msgstr "Wij bieden advies voor het opschonen van malware"

#: admin/wp-security-filescan-menu.php:382
msgid "Blacklist removal"
msgstr "Blacklist verwijderen"

#: admin/wp-security-filescan-menu.php:383
msgid "No contract (cancel anytime)"
msgstr "Geen contract (annuleren Anytime)"

#: admin/wp-security-filescan-menu.php:385
msgid "To learn more please %s."
msgstr "%s om meer te leren."

#: admin/wp-security-filescan-menu.php:406
msgid "Latest file change scan results"
msgstr "Laatste resultaten scan van bestandswijziging"

#: admin/wp-security-filescan-menu.php:416
msgid "The following files were added to your host."
msgstr "De volgende bestanden zijn toegevoegd aan je host"

#: admin/wp-security-filescan-menu.php:419
#: admin/wp-security-filescan-menu.php:440
#: admin/wp-security-filescan-menu.php:464
msgid "File"
msgstr "Bestand"

#: admin/wp-security-filescan-menu.php:420
#: admin/wp-security-filescan-menu.php:441
#: admin/wp-security-filescan-menu.php:465
msgid "File size"
msgstr "Bestandsgrootte"

#: admin/wp-security-filescan-menu.php:421
#: admin/wp-security-filescan-menu.php:442
#: admin/wp-security-filescan-menu.php:466
msgid "File modified"
msgstr "Bestand bewerkt"

#: admin/wp-security-filescan-menu.php:437
msgid "The following files were removed from your host."
msgstr "De volgende regels zijn verwijderd van jouw host"

#: admin/wp-security-filescan-menu.php:461
msgid "The following files were changed on your host."
msgstr "De volgende regels zijn bewerkt op jouw host"

#: admin/wp-security-filesystem-menu.php:26
#: classes/grade-system/wp-security-feature-item-manager.php:69
msgid "File permissions"
msgstr "Bestandsrechten"

#: admin/wp-security-filesystem-menu.php:27
msgid "PHP file editing"
msgstr "PHP-bestand bewerken"

#: admin/wp-security-filesystem-menu.php:28
msgid "WP file access"
msgstr "WP-bestandstoegang"

#: admin/wp-security-filesystem-menu.php:29
msgid "Host system logs"
msgstr "Host systeemlogs"

#: admin/wp-security-filesystem-menu.php:55
msgid "Filesystem security"
msgstr "Bestandsbeveiliging"

#: admin/wp-security-filesystem-menu.php:80
msgid "Nonce check failed for manual DB backup operation!"
msgstr "Nonce controle mislukt voor handmatige DB-back-up!"

#: admin/wp-security-filesystem-menu.php:90
msgid "The permissions for %s were succesfully changed to %s"
msgstr "De machtigingen voor %s zijn met succes gewijzigd in %s"

#: admin/wp-security-filesystem-menu.php:94
msgid "Unable to change permissions for %s!"
msgstr "Kan de machtigingen voor %s niet wijzigen!"

#: admin/wp-security-filesystem-menu.php:100
msgid "File permissions scan"
msgstr "Scan bestandsrechten"

#: admin/wp-security-filesystem-menu.php:103
msgid "Your WordPress file and folder permission settings govern the accessability and read/write privileges of the files and folders which make up your WP installation."
msgstr "Uw instellingen van permissies voor WordPress-bestanden en mappen regelen de toegankelijkheid en lees/schrijfprivileges van de bestanden en mappen die uw WP-installatie vormen."

#: admin/wp-security-filesystem-menu.php:104
msgid "Your WP installation already comes with reasonably secure file permission settings for the filesystem."
msgstr "Uw WP-installatie komt al met redelijk veilige instellingen van bestandspermissie voor het bestandssysteem."

#: admin/wp-security-filesystem-menu.php:105
msgid "However, sometimes people or other plugins modify the various permission settings of certain core WP folders or files such that they end up making their site less secure because they chose the wrong permission values."
msgstr "Echter, soms wijzigen mensen of andere plugins de verschillende toegangsrechten van bepaalde core WP-mappen of bestanden zodanig dat ze uiteindelijk de site minder veilig maken omdat ze kozen voor de verkeerde toegangsrechten."

#: admin/wp-security-filesystem-menu.php:106
msgid "This feature will scan the critical WP core folders and files and will highlight any permission settings which are insecure."
msgstr "Deze functie scant de kritische WP core mappen en bestanden, en zal alle toegangsrechten die onveilig zijn markeren."

#: admin/wp-security-filesystem-menu.php:114
msgid "This plugin has detected that your site is running on a Windows server."
msgstr "Deze plugin heeft ontdekt dat jouw site draait op een Windows-server."

#: admin/wp-security-filesystem-menu.php:115
msgid "This feature is not applicable for Windows server installations."
msgstr "Deze mogelijkheid is niet beschikbaar voor installaties die draaien op een Windows-server."

#: admin/wp-security-filesystem-menu.php:121
msgid "WP directory and file permissions scan results"
msgstr "Resultaten scan WP-directory en bestandspermissies"

#: admin/wp-security-filesystem-menu.php:133
#: admin/wp-security-filesystem-menu.php:152
msgid "Name"
msgstr "Naam"

#: admin/wp-security-filesystem-menu.php:134
#: admin/wp-security-filesystem-menu.php:153
msgid "File/Folder"
msgstr "Bestand / Map"

#: admin/wp-security-filesystem-menu.php:135
#: admin/wp-security-filesystem-menu.php:154
msgid "Current permissions"
msgstr "Huidge rechten"

#: admin/wp-security-filesystem-menu.php:136
#: admin/wp-security-filesystem-menu.php:155
msgid "Recommended permissions"
msgstr "Aangeraden vechten"

#: admin/wp-security-filesystem-menu.php:137
#: admin/wp-security-filesystem-menu.php:156
msgid "Recommended action"
msgstr "Aangeraden actie"

#: admin/wp-security-filesystem-menu.php:195
msgid "Your PHP file editing settings were saved successfully."
msgstr "Uw instellingen voor bewerken PHP-bestand werden met succes opgeslagen."

#: admin/wp-security-filesystem-menu.php:199
msgid "Operation failed! Unable to modify or make a backup of wp-config.php file!"
msgstr "Operatie mislukt! Niet in staat om wp-config. php-bestand te wijzigen of een back-up te maken!"

#: admin/wp-security-filesystem-menu.php:212
#: classes/grade-system/wp-security-feature-item-manager.php:71
msgid "File editing"
msgstr "Bestand bewerken"

#: admin/wp-security-filesystem-menu.php:215
msgid "The WordPress Dashboard by default allows administrators to edit PHP files, such as plugin and theme files."
msgstr "Standaard zal het WordPress-dashboard beheerders toestaan om PHP-bestanden te bewerken, zoals plugin- en thema-bestanden."

#: admin/wp-security-filesystem-menu.php:216
msgid "This is often the first tool an attacker will use if able to login, since it allows code execution."
msgstr "Dit is vaak het eerste hulpmiddel dat een aanvaller zal gebruiken als hij kan inloggen, aangezien het code-uitvoering toestaat."

#: admin/wp-security-filesystem-menu.php:217
msgid "This feature will disable the ability for people to edit PHP files via the dashboard."
msgstr "Deze functie zal de mogelijkheid uitschakenlen om PHP-bestanden te bewerken via het dashboard."

#: admin/wp-security-filesystem-menu.php:223
msgid "Disable PHP file editing"
msgstr "PHP-bestand bewerken uitzetten"

#: admin/wp-security-filesystem-menu.php:235
msgid "Disable ability to edit PHP files"
msgstr "PHP-bestand bewerken uitzetten"

#: admin/wp-security-filesystem-menu.php:238
msgid "Check this if you want to remove the ability for people to edit PHP files via the WP dashboard"
msgstr "Vink dit aan als je de mogelijkheid tot het bewerken van PHP via het WordPress-dashboard uit wilt zetten"

#: admin/wp-security-filesystem-menu.php:282
msgid "You have successfully saved the Prevent Access to Default WP Files configuration."
msgstr "Je hebt succesvol de instellingen opgeslagen voor het voorkomen van toegang tot WP-bestanden."

#: admin/wp-security-filesystem-menu.php:286
#: admin/wp-security-firewall-menu.php:126
#: admin/wp-security-firewall-menu.php:346
#: admin/wp-security-firewall-menu.php:613
#: admin/wp-security-firewall-menu.php:912
#: admin/wp-security-settings-menu.php:772
#: admin/wp-security-spam-menu.php:124
msgid "Could not write to the .htaccess file. Please check the file permissions."
msgstr "Kan .htaccess-bestand niet schrijven. Controleer bestandsrechten."

#: admin/wp-security-filesystem-menu.php:291
msgid "WordPress files"
msgstr "WordPress-bestanden"

#: admin/wp-security-filesystem-menu.php:294
msgid "This feature allows you to prevent access to files such as %s, %s and %s which are delivered with all WP installations."
msgstr "Deze optie blokkeert toegang tot bestanden zoals %s, %s en %s die standaard met WP meekomen."

#: admin/wp-security-filesystem-menu.php:295
msgid "By preventing access to these files you are hiding some key pieces of information (such as WordPress version info) from potential hackers."
msgstr "Door toegang tot deze bestanden te blokkeren kan je belangrijke informatie afschermen (zoals welke WordPress-versie)."

#: admin/wp-security-filesystem-menu.php:300
msgid "Prevent access to default WP files"
msgstr "Toegang tot standaard WP-bestanden uitzetten"

#: admin/wp-security-filesystem-menu.php:311
msgid "Prevent access to WP default install files"
msgstr "Toegang tot WP-bestand blokkeren"

#: admin/wp-security-filesystem-menu.php:314
msgid "Check this if you want to prevent access to readme.html, license.txt and wp-config-sample.php."
msgstr "Vink dit aan als je toegang tot readme.html, license.txt en wp-config-sample.php wil blokkeren."

#: admin/wp-security-filesystem-menu.php:318
msgid "Save setting"
msgstr "Instellingen opslaan"

#: admin/wp-security-filesystem-menu.php:342
msgid "System logs"
msgstr "Systeembestanden"

#: admin/wp-security-filesystem-menu.php:345
msgid "Sometimes your hosting platform will produce error or warning logs in a file called \"error_log\"."
msgstr "Soms zal uw hosting-platform fout- of waarschuwingslogs produceren in een bestand genaamd \"error_log\"."

#: admin/wp-security-filesystem-menu.php:346
msgid "Depending on the nature and cause of the error or warning, your hosting server can create multiple instances of this file in numerous directory locations of your WordPress installation."
msgstr "Afhankelijk van de aard en de oorzaak van de fout of waarschuwing, kan uw hosting server meerdere exemplaren van dit bestand aanmaken in verschillende mappen van uw WordPress-installatie."

#: admin/wp-security-filesystem-menu.php:347
msgid "By occassionally viewing the contents of these logs files you can keep informed of any underlying problems on your system which you might need to address."
msgstr "Door af en toe de inhoud van deze log-bestanden te bekijken blijft u op de hoogte van eventuele onderliggende problemen op uw systeem die misschien aangepakt moeten worden."

#: admin/wp-security-filesystem-menu.php:353
msgid "View system logs"
msgstr "Bekijk systeemlogs"

#: admin/wp-security-filesystem-menu.php:355
msgid "Please click the button below to view the latest system logs"
msgstr ""

#: admin/wp-security-filesystem-menu.php:358
msgid "Enter System Log File Name"
msgstr "Vul bestandsnaam systeemlog in"

#: admin/wp-security-filesystem-menu.php:360
msgid "Enter your system log file name. (Defaults to error_log)"
msgstr "Vul bestandsnaam van je systeemlog in (Standaard is error_log)"

#: admin/wp-security-filesystem-menu.php:363
msgid "View latest system logs"
msgstr "Toon meest recente systeemlogs"

#: admin/wp-security-filesystem-menu.php:365
msgid "Loading..."
msgstr "Laden..."

#: admin/wp-security-filesystem-menu.php:382
msgid "No system logs were found."
msgstr "Geen systeemlogs gevonden!"

#: admin/wp-security-filesystem-menu.php:435
msgid "Set recommended permissions"
msgstr "Aanbevolen permissies instellen"

#: admin/wp-security-filesystem-menu.php:441
msgid "No action required"
msgstr "Geen actie nodig."

#: admin/wp-security-filesystem-menu.php:481
msgid "Showing latest entries of error_log file: %s"
msgstr "Toont laatste vermeldingen uit het error_log bestand: %s"

#: admin/wp-security-firewall-menu.php:28
msgid "Basic firewall rules"
msgstr "Standaard firewall-regels"

#: admin/wp-security-firewall-menu.php:29
msgid "Additional firewall rules"
msgstr "Extra firewall-regels"

#: admin/wp-security-firewall-menu.php:30
msgid "6G Blacklist firewall rules"
msgstr "6G Blacklist firewall-regels"

#: admin/wp-security-firewall-menu.php:31
msgid "Internet bots"
msgstr "Internet bots"

#: admin/wp-security-firewall-menu.php:32
msgid "Prevent hotlinks"
msgstr "Hotlinks voorkomen"

#: admin/wp-security-firewall-menu.php:33
msgid "404 detection"
msgstr "404-detectie"

#: admin/wp-security-firewall-menu.php:34
msgid "Custom rules"
msgstr "Aangepaste regels"

#: admin/wp-security-firewall-menu.php:122
#: admin/wp-security-firewall-menu.php:908
#: admin/wp-security-spam-menu.php:120
#: admin/wp-security-spam-menu.php:494
#: admin/wp-security-spam-menu.php:556
#: admin/wp-security-user-registration-menu.php:95
msgid "Settings were successfully saved"
msgstr "Instelling zijn succesvol opgeslagen"

#: admin/wp-security-firewall-menu.php:131
#: admin/wp-security-firewall-menu.php:651
msgid "Firewall settings"
msgstr "Firewall-instellingen"

#: admin/wp-security-firewall-menu.php:138
msgid "This should not have any impact on your site's general functionality but if you wish you can take a %s of your .htaccess file before proceeding."
msgstr "Dit zou geen invloed op de algemene functionaliteit van uw site moeten hebben, maar als je wilt, kun je een %s van je .htaccess-bestand maken voordat je verder gaat."

#: admin/wp-security-firewall-menu.php:139
msgid "The features in this tab allow you to activate some basic firewall security protection rules for your site."
msgstr "Met de mogelijkheden in dit tabblad kunt u een aantal elementaire firewall-beveiligingsregels activeren voor uw site."

#: admin/wp-security-firewall-menu.php:140
msgid "The firewall functionality is achieved via the insertion of special code into your currently active .htaccess file."
msgstr "De firewall-functionaliteit wordt bereikt door het inbrengen van speciale code in uw huidige actieve .htaccess-bestand."

#: admin/wp-security-firewall-menu.php:151
msgid "You have enabled the \"Completely Block Access To XMLRPC\" checkbox which means all XMLRPC functionality will be blocked."
msgstr "Let op: U hebt het selectievakje \"Volledig blokkeren van toegang tot XML-RPC\" ingeschakeld, wat betekent dat alle XML-RPC-functionaliteit zal worden geblokkeerd ."

#: admin/wp-security-firewall-menu.php:152
msgid "By leaving this feature enabled you will prevent Jetpack or Wordpress iOS or other apps which need XMLRPC from working correctly on your site."
msgstr "Als u deze functie ingeschakeld laat , voorkomt u dat Jetpack of WordPress iOS of andere apps die XML-RPC nodig hebben correct werken op uw site ."

#: admin/wp-security-firewall-menu.php:153
msgid "If you still need XMLRPC then uncheck the \"Completely Block Access To XMLRPC\" checkbox and enable only the \"Disable Pingback Functionality From XMLRPC\" checkbox."
msgstr "Als u nog steeds XML-RPC nodig hebt, schakelt u het selectievakje 'Volledig blokkeren van toegang tot XML-RPC' uit en schakelt u alleen het selectievakje 'Pingback-functionaliteit van XML-RPC uitschakelen' in."

#: admin/wp-security-firewall-menu.php:163
msgid "Basic firewall settings"
msgstr "Standaard firewall-instellingen"

#: admin/wp-security-firewall-menu.php:171
msgid "Enable basic firewall protection"
msgstr "Standaard firewall-bescherming gebruiken"

#: admin/wp-security-firewall-menu.php:174
msgid "Check this if you want to apply basic firewall protection to your site."
msgstr "Activeer dit voor elementaire firewall-bescherming van uw site."

#: admin/wp-security-firewall-menu.php:178
msgid "This setting will implement the following basic firewall protection mechanisms on your site:"
msgstr "Deze instelling zal de volgende elementaire firewall-beveiligingsmechanismen op uw site implementeren:"

#: admin/wp-security-firewall-menu.php:179
msgid "1) Protect your htaccess file by denying access to it."
msgstr "1) Bescherm uw .htaccess-bestand door toegang tot het bestand te weigeren."

#: admin/wp-security-firewall-menu.php:180
msgid "2) Disable the server signature."
msgstr "2) Schakel de server handtekening uit."

#: admin/wp-security-firewall-menu.php:181
msgid "3) Limit file upload size (%sMB)."
msgstr ""

#: admin/wp-security-firewall-menu.php:182
msgid "4) Protect your wp-config.php file by denying access to it."
msgstr "4) Bescherm uw wp-config.php-bestand door toegang tot het bestand te weigeren."

#: admin/wp-security-firewall-menu.php:183
msgid "The above firewall features will be applied via your .htaccess file and should not affect your site's overall functionality."
msgstr "De bovenstaande firewall-functies zullen worden toegepast via uw .htaccess-bestand en mogen niet van invloed zijn op de algehele functionaliteit van uw site."

#: admin/wp-security-firewall-menu.php:184
msgid "You are still advised to take a backup of your active .htaccess file just in case."
msgstr "U wordt nog steeds geadviseerd om een back-up van uw actieve .htaccess-bestand te maken."

#: admin/wp-security-firewall-menu.php:190
msgid "Max file upload size (MB)"
msgstr ""

#: admin/wp-security-firewall-menu.php:192
msgid "The value for the maximum file upload size used in the .htaccess file. (Defaults to %sMB if left blank)"
msgstr ""

#: admin/wp-security-firewall-menu.php:200
msgid "WordPress XMLRPC and pingback vulnerability protection"
msgstr ""

#: admin/wp-security-firewall-menu.php:208
msgid "Completely block access to XMLRPC"
msgstr "Volledig blokkeren toegang tot XML-RPC"

#: admin/wp-security-firewall-menu.php:211
msgid "Check this if you are not using the WP XML-RPC functionality and you want to completely block external access to XMLRPC."
msgstr "Vink dit aan als u de WP XML-RPC-functionaliteit niet gebruikt en u de externe toegang tot XML-RPC volledig wilt blokkeren ."

#: admin/wp-security-firewall-menu.php:215
msgid "This setting will add a directive in your .htaccess to disable access to the WordPress xmlrpc.php file which is responsible for the XML-RPC functionality in WordPress."
msgstr "Deze instelling zal een regel toevoegen in uw .htaccess-bestand om de toegang tot de WordPress xmlrpc.php bestand dat verantwoordelijk is voor de XML-RPC-functionaliteit in WordPress uit te schakelen."

#: admin/wp-security-firewall-menu.php:216
msgid "Hackers can exploit various vulnerabilities in the WordPress XML-RPC API in a number of ways such as:"
msgstr "Hackers kunnen gebruik maken van verschillende kwetsbaarheden in de WordPress XML-RPC API op een aantal manieren, zoals:"

#: admin/wp-security-firewall-menu.php:217
msgid "1) Denial of Service (DoS) attacks"
msgstr "1) Denial of Service (DoS) aanvallen"

#: admin/wp-security-firewall-menu.php:218
msgid "2) Hacking internal routers."
msgstr "2) Hacking interne routers."

#: admin/wp-security-firewall-menu.php:219
msgid "3) Scanning ports in internal networks to get info from various hosts."
msgstr "3) Poorten scannen in interne netwerken om informatie van verschillende hosts te krijgen."

#: admin/wp-security-firewall-menu.php:220
msgid "Apart from the security protection benefit, this feature may also help reduce load on your server, particularly if your site currently has a lot of unwanted traffic hitting the XML-RPC API on your installation."
msgstr "Afgezien van het beveiligingsvoordeel, kan deze functie ook helpen bij het verminderen van de belasting op de server, zeker als uw site op dit moment last heeft van veel ongewenst verkeer die de XML-RPC API van uw installatie misbruiken."

#: admin/wp-security-firewall-menu.php:221
msgid "NOTE: You should only enable this feature if you are not currently using the XML-RPC functionality on your WordPress installation."
msgstr "OPMERKING: U moet deze functie alleen inschakelen als u momenteel de XML-RPC-functionaliteit op uw WordPress-installatie niet gebruikt."

#: admin/wp-security-firewall-menu.php:222
msgid "Leave this feature disabled and use the feature below if you want pingback protection but you still need XMLRPC."
msgstr "Laat deze functie uitgeschakeld en gebruik de onderstaande functie als je pingback-beveiliging wilt, maar je hebt nog steeds XML-RPC nodig."

#: admin/wp-security-firewall-menu.php:228
msgid "Disable pingback functionality from XMLRPC"
msgstr "Schakel Pingback-functionaliteit uit vanuit XMLRPC"

#: admin/wp-security-firewall-menu.php:231
msgid "If you use Jetpack or WP iOS or other apps which need WP XML-RPC functionality then check this. This will enable protection against WordPress pingback vulnerabilities."
msgstr "Als u Jetpack of WP iOS of andere apps gebruikt die WP XML-RPC-functionaliteit nodig hebben, vinkt u dit aan. Hiermee wordt beveiliging tegen WordPress-pingback-kwetsbaarheden mogelijk gemaakt."

#: admin/wp-security-firewall-menu.php:235
msgid "NOTE: If you use Jetpack or the Wordpress iOS or other apps then you should enable this feature but leave the \"Completely Block Access To XMLRPC\" checkbox unchecked."
msgstr "OPMERKING: Als u Jetpack of WordPress iOS of andere apps gebruikt dan moet je deze functie inschakelen, maar laat de \"Volledig blokkeren Access To XML-RPC\" checkbox niet aangevinkt."

#: admin/wp-security-firewall-menu.php:236
msgid "The feature will still allow XMLRPC functionality on your site but will disable the pingback methods."
msgstr "De functie zal nog steeds XMLRPC-functionaliteit op uw site toestaan, maar zal de pingback-methoden uitschakelen."

#: admin/wp-security-firewall-menu.php:237
msgid "This feature will also remove the \"X-Pingback\" header if it is present."
msgstr "Deze functie verwijdert ook de \"X-Pingback\" header als deze aanwezig is."

#: admin/wp-security-firewall-menu.php:246
msgid "Block access to debug log file"
msgstr "Toegang blokkeren tot het debug-logbestand"

#: admin/wp-security-firewall-menu.php:254
msgid "Block access to debug.log file"
msgstr "Blokkeer de toegang tot debug.log bestand"

#: admin/wp-security-firewall-menu.php:257
msgid "Check this if you want to block access to the debug.log file that WordPress creates when debug logging is enabled."
msgstr "Markeer dit wanneer u de toegang tot de file debug.log wil blokkeren, die WordPress aanmaakt als de debug-log aan staat."

#: admin/wp-security-firewall-menu.php:261
msgid "WordPress has an option to turn on the debug logging to a file located in wp-content/debug.log. This file may contain sensitive information."
msgstr "WordPress heeft een optie om de debug-logging aan te zetten naar een bestand in wp-content/debug. log. Dit bestand kan gevoelige informatie bevatten."

#: admin/wp-security-firewall-menu.php:262
msgid "Using this option will block external access to this file."
msgstr ""

#: admin/wp-security-firewall-menu.php:262
msgid "You can still access this file by logging into your site via FTP."
msgstr ""

#: admin/wp-security-firewall-menu.php:270
msgid "Save basic firewall settings"
msgstr "Standaard firewall-instellingen opslaan"

#: admin/wp-security-firewall-menu.php:342
msgid "You have successfully saved the Additional Firewall Protection configuration"
msgstr "Je hebt de configuratie voor Extra Firewall Protection succesvol opgeslagen"

#: admin/wp-security-firewall-menu.php:356
msgid "Additional firewall protection"
msgstr "Extra firewall-bescherming"

#: admin/wp-security-firewall-menu.php:360
msgid "Due to the nature of the code being inserted to the .htaccess file, this feature may break some functionality for certain plugins and you are therefore advised to take a %s of .htaccess before applying this configuration."
msgstr "Vanwege de aard van de code die in het .htaccess-bestand wordt geplaatst, kan deze functie sommige functies voor bepaalde plugins dwars zitten. U wordt daarom geadviseerd om %s van .htaccess-bestand te maken voordat u deze configuratie toepast."

#: admin/wp-security-firewall-menu.php:362
msgid "This feature allows you to activate more advanced firewall settings to your site."
msgstr "Deze functie stelt u in staat om de meer geavanceerde firewall-instellingen voor uw site te activeren."

#: admin/wp-security-firewall-menu.php:363
msgid "The advanced firewall rules are applied via the insertion of special code to your currently active .htaccess file."
msgstr "De geavanceerde firewall-regels worden via het inbrengen van speciale code toegepast op uw huidige actieve .htaccess-bestand."

#: admin/wp-security-firewall-menu.php:372
msgid "Listing of directory contents"
msgstr "Lijst van inhoud van de folder"

#: admin/wp-security-firewall-menu.php:381
#: classes/grade-system/wp-security-feature-item-manager.php:85
msgid "Disable index views"
msgstr "Index weergaven uitschakelen"

#: admin/wp-security-firewall-menu.php:384
msgid "Check this if you want to disable directory and file listing."
msgstr "Activeer dit als u de mogelijkheid voor map- en bestandslijsten uit wilt schakelen."

#: admin/wp-security-firewall-menu.php:389
msgid "By default, an Apache server will allow the listing of the contents of a directory if it doesn't contain an index.php file."
msgstr "Standaard staat een Apache-server het toe om een lijst te tonen van de inhoud van een map als de map geen index.php bestand bevat."

#: admin/wp-security-firewall-menu.php:391
msgid "This feature will prevent the listing of contents for all directories."
msgstr "Deze functie voorkomt het tonen van een lijst met de inhoud voor alle mappen."

#: admin/wp-security-firewall-menu.php:393
msgid "NOTE: In order for this feature to work \"AllowOverride\" of the Indexes directive must be enabled in your httpd.conf file. Ask your hosting provider to check this if you don't have access to httpd.conf"
msgstr "OPMERKING: Om deze functie te laten werken dient \"AllowOverride\" van de Indexes richtlijn te worden ingeschakeld in uw httpd.conf-bestand. Vraag uw hosting provider om dit te controleren als u geen toegang hebt tot het httpd.conf-bestand heeft"

#: admin/wp-security-firewall-menu.php:402
msgid "Trace and track"
msgstr "Trace and Track"

#: admin/wp-security-firewall-menu.php:411
#: classes/grade-system/wp-security-feature-item-manager.php:86
msgid "Disable trace and track"
msgstr "Trace and Track uitzetten"

#: admin/wp-security-firewall-menu.php:414
msgid "Check this if you want to disable trace and track."
msgstr "Activeer dit als u traceren en volgen (track & trace) uit wilt schakelen."

#: admin/wp-security-firewall-menu.php:419
msgid "HTTP Trace attack (XST) can be used to return header requests and grab cookies and other information."
msgstr "HTTP Trace aanval (XST) kan worden gebruikt om header verzoeken en cookies op te pakken en andere informatie terug te geven."

#: admin/wp-security-firewall-menu.php:421
msgid "This hacking technique is usually used together with cross site scripting attacks (XSS)."
msgstr "Deze hack-techniek wordt meestal gebruikt samen met de cross site scripting-aanvallen (XSS)."

#: admin/wp-security-firewall-menu.php:423
msgid "Disabling trace and track on your site will help prevent HTTP Trace attacks."
msgstr "Het uitschakelen van traceren en volgen (trace & track) op uw site zal HTTP Trace-aanslagen helpen voorkomen."

#: admin/wp-security-firewall-menu.php:432
msgid "Proxy comment posting"
msgstr "Reactie plaatsen via proxy"

#: admin/wp-security-firewall-menu.php:442
msgid "Forbid proxy comment posting"
msgstr "Reactie plaatsen via proxy blokkeren"

#: admin/wp-security-firewall-menu.php:445
msgid "Check this if you want to forbid proxy comment posting."
msgstr "Vink dit aan als je niet wil dat reacties via een proxy worden geplaatst."

#: admin/wp-security-firewall-menu.php:450
msgid "This setting will deny any requests that use a proxy server when posting comments."
msgstr "Deze instelling zal alle verzoeken weigeren die gebruik maken van een proxy-server bij het plaatsen van reacties."

#: admin/wp-security-firewall-menu.php:451
msgid "By forbidding proxy comments you are in effect eliminating some spam and other proxy requests."
msgstr "Door het verbieden van proxy-opmerkingen heft u in feite bepaalde SPAM en andere proxy-verzoeken op."

#: admin/wp-security-firewall-menu.php:460
msgid "Bad query strings"
msgstr "Ongeldige query tekenreeksen"

#: admin/wp-security-firewall-menu.php:470
msgid "Deny bad query strings"
msgstr "Ongeldige query tekenreeksen weigeren"

#: admin/wp-security-firewall-menu.php:473
msgid "This will help protect you against malicious queries via XSS."
msgstr "Dit zal helpen om u te beschermen tegen kwaadaardige queries via XSS."

#: admin/wp-security-firewall-menu.php:478
msgid "This feature will write rules in your .htaccess file to prevent malicious string attacks on your site using XSS."
msgstr "Deze functie zal regels in uw .htaccess-bestand schrijven om kwaadaardige tekst aanvallen op uw site met behulp van XSS te voorkomen."

#: admin/wp-security-firewall-menu.php:479
msgid "NOTE: Some of these strings might be used for plugins or themes and hence this might break some functionality."
msgstr "OPMERKING: Sommige van deze teksten kunnen worden gebruikt voor plugins of thema's en dus kan dit sommige functionaliteit te niet doen."

#: admin/wp-security-firewall-menu.php:480
#: admin/wp-security-firewall-menu.php:510
msgid "You are therefore strongly advised to take a backup of your active .htaccess file before applying this feature."
msgstr "U wordt daarom sterk aangeraden om een back-up van uw actieve .htaccess-bestand te maken alvorens deze functie te activeren."

#: admin/wp-security-firewall-menu.php:489
#: classes/grade-system/wp-security-feature-item-manager.php:89
msgid "Advanced character string filter"
msgstr "Geavanceerd tekstfilter"

#: admin/wp-security-firewall-menu.php:499
msgid "Enable advanced character string filter"
msgstr "Inschakelen geavanceerd tekstfilter"

#: admin/wp-security-firewall-menu.php:502
msgid "This will block bad character matches from XSS."
msgstr "Dit zal kwaadaardige karakter overeenkomsten van XSS blokkeren."

#: admin/wp-security-firewall-menu.php:507
msgid "This is an advanced character string filter to prevent malicious string attacks on your site coming from Cross Site Scripting (XSS)."
msgstr "Dit is een geavanceerd tekenreeksfilter om kwaadaardige aanvallen op uw site dmv Cross Site Scripting (XSS) te voorkomen."

#: admin/wp-security-firewall-menu.php:508
msgid "This setting matches for common malicious string patterns and exploits and will produce a 403 error for the hacker attempting the query."
msgstr "Deze instelling zoekt overeenkomsten met veel voorkomende kwaadaardige reekspatronen en exploits en zal een 403-foutmelding genereren als de hacker de query uitprobeert."

#: admin/wp-security-firewall-menu.php:509
msgid "NOTE: Some strings for this setting might break some functionality."
msgstr "OPMERKING: Sommige reeksen voor deze instelling kunnen sommige functies te niet doen."

#: admin/wp-security-firewall-menu.php:518
msgid "Save additional firewall settings"
msgstr "Extra firewall-instellingen opslaan"

#: admin/wp-security-firewall-menu.php:609
msgid "You have successfully saved the 5G/6G Firewall Protection configuration"
msgstr "Je hebt de 5G/6G Firewall-bescherming opgeslagen"

#: admin/wp-security-firewall-menu.php:633
msgid "All in One WP Security and Firewall"
msgstr ""

#: admin/wp-security-firewall-menu.php:634
msgid "We were unable to access the firewall's configuration file:"
msgstr ""

#: admin/wp-security-firewall-menu.php:636
msgid "As a result, the firewall will be unavailable."
msgstr ""

#: admin/wp-security-firewall-menu.php:637
msgid "Please check your PHP error log for further information."
msgstr ""

#: admin/wp-security-firewall-menu.php:638
msgid "If you're unable to locate your PHP log file, please contact your web hosting company to ask them where it can be found on their setup."
msgstr ""

#: admin/wp-security-firewall-menu.php:655
msgid "This feature allows you to activate the %s (or legacy %s) firewall security protection rules designed and produced by %s."
msgstr "Deze functie maakt het mogelijk dat u de beveiligingsregels van de firewall voor %s (of legacy %s) die zijn ontworpen en geproduceerd door %s, te activeren."

#: admin/wp-security-firewall-menu.php:656
msgid "The 6G Blacklist is updated and improved version of 5G Blacklist. If you have 5G Blacklist active, you might consider activating 6G Blacklist instead."
msgstr "De 6G Blacklist is een bijgewerkte en verbeterde versie van 5G Blacklist. Als je de 5G-blacklist actief hebt, kun je overwegen om in plaats daarvan de 6G Blacklist te activeren."

#: admin/wp-security-firewall-menu.php:657
msgid "The 6G Blacklist is a simple, flexible blacklist that helps reduce the number of malicious URL requests that hit your website."
msgstr "De 6G zwarte lijst is een eenvoudige, flexibele zwarte lijst die helpt bij het verminderen van het aantal kwaadaardige URL-verzoeken die uw website bereiken."

#: admin/wp-security-firewall-menu.php:658
msgid "The added advantage of applying the 6G firewall to your site is that it has been tested and confirmed by the people at PerishablePress.com to be an optimal and least disruptive set of .htaccess security rules for general WP sites running on an Apache server or similar."
msgstr "Het extra voordeel van de toepassing van de 6G firewall op uw site is dat het is getest en bevestigd is door de mensen van PerishablePress.com dat het om een optimale en minst ontwrichtende set van. htaccess-beveiligingsregels gaat, voor algemene WP-sites die draaien op een Apache-server of iets dergelijks."

#: admin/wp-security-firewall-menu.php:659
msgid "Therefore the 6G firewall rules should not have any impact on your site's general functionality but if you wish you can take a %s of your .htaccess file before proceeding."
msgstr "Daarom zouden de 6G firewall-regels geen invloed op de algemene functionaliteit van uw site moeten hebben, maar als u wenst kunt u %s van uw. htaccess-bestand maken alvorens te werk te gaan."

#: admin/wp-security-firewall-menu.php:665
msgid "6G blacklist/firewall settings"
msgstr "6G Zwarte lijst/Firewall-instellingen"

#: admin/wp-security-firewall-menu.php:677
msgid "Enable 6G firewall protection"
msgstr "6G Firewall-bescherming inschakelen"

#: admin/wp-security-firewall-menu.php:680
msgid "Check this if you want to apply the 6G Blacklist firewall protection from perishablepress.com to your site."
msgstr "Vink dit aan als u de 6G Blacklist firewall-bescherming van perishablepress.com op uw site wilt toepassen ."

#: admin/wp-security-firewall-menu.php:684
msgid "This setting will implement the 6G security firewall protection mechanisms on your site which include the following things:"
msgstr "Deze instelling zal de 6G Security Firewall beschermingsmechanismen op uw site implementeren welke de volgende zaken omvatten:"

#: admin/wp-security-firewall-menu.php:685
#: admin/wp-security-firewall-menu.php:703
msgid "1) Block forbidden characters commonly used in exploitative attacks."
msgstr "1) Blokkeer verboden karakters die vaak gebruikt worden in exploiterende aanvallen."

#: admin/wp-security-firewall-menu.php:686
#: admin/wp-security-firewall-menu.php:704
msgid "2) Block malicious encoded URL characters such as the \".css(\" string."
msgstr "2) Blokkeer kwaadaardige gecodeerde URL-tekens zoals de \".css(\" string."

#: admin/wp-security-firewall-menu.php:687
#: admin/wp-security-firewall-menu.php:705
msgid "3) Guard against the common patterns and specific exploits in the root portion of targeted URLs."
msgstr "3) Bescherm tegen algemene patronen en specifieke exploits in het basisdeel van beoogde URL's."

#: admin/wp-security-firewall-menu.php:688
#: admin/wp-security-firewall-menu.php:706
msgid "4) Stop attackers from manipulating query strings by disallowing illicit characters."
msgstr "4) Stop het manipuleren van querytekenreeksen door aanvallers door illegale karakters niet toe te staan."

#: admin/wp-security-firewall-menu.php:689
#: admin/wp-security-firewall-menu.php:707
msgid "....and much more."
msgstr "....en veel meer."

#: admin/wp-security-firewall-menu.php:695
msgid "Enable legacy 5G firewall protection"
msgstr "Verouderde 5G-firewall-bescherming inschakelen"

#: admin/wp-security-firewall-menu.php:698
msgid "Check this if you want to apply the 5G Blacklist firewall protection from perishablepress.com to your site."
msgstr "Activeer dit als u de 5G Blacklist firewall-bescherming van perishablepress.com wilt toepassen op uw site."

#: admin/wp-security-firewall-menu.php:702
msgid "This setting will implement the 5G security firewall protection mechanisms on your site which include the following things:"
msgstr "Deze instelling zal de 5G firewall-beschermingsmechanismen op uw site implementeren. Het omvat de volgende zaken:"

#: admin/wp-security-firewall-menu.php:713
msgid "Save 5G/6G firewall settings"
msgstr "5G/6G Firewall-instellingen opslaan"

#: admin/wp-security-firewall-menu.php:721
msgid "6G block request methods"
msgstr ""

#: admin/wp-security-firewall-menu.php:725
msgid "HTTP Request methods are used by browsers and clients to communicate with servers to get responses."
msgstr ""

#: admin/wp-security-firewall-menu.php:726
msgid "GET and POST are the most commonly used methods to request and submit data for specified resources of the server."
msgstr ""

#: admin/wp-security-firewall-menu.php:732
msgid "Block %s method"
msgstr ""

#: admin/wp-security-firewall-menu.php:735
msgid "Check this to block the %s request method"
msgstr ""

#: admin/wp-security-firewall-menu.php:740
msgid "Some WooCommerce extensions use the PUT request method in addition to GET and POST."
msgstr ""

#: admin/wp-security-firewall-menu.php:740
msgid "This means WooCommerce users shouldn't block the PUT request method."
msgstr ""

#: admin/wp-security-firewall-menu.php:741
msgid "A few REST requests use the PUT request method."
msgstr ""

#: admin/wp-security-firewall-menu.php:741
msgid "If your site is communicated by the WP REST API, you should not block the PUT request method."
msgstr ""

#: admin/wp-security-firewall-menu.php:749
msgid "Save request methods settings"
msgstr ""

#: admin/wp-security-firewall-menu.php:757
msgid "6G other settings"
msgstr ""

#: admin/wp-security-firewall-menu.php:761
msgid "Block query strings"
msgstr ""

#: admin/wp-security-firewall-menu.php:764
msgid "Check this to block all query strings recommended by 6G"
msgstr ""

#: admin/wp-security-firewall-menu.php:768
msgid "Block request strings"
msgstr ""

#: admin/wp-security-firewall-menu.php:771
msgid "Check this to block all request strings recommended by 6G"
msgstr ""

#: admin/wp-security-firewall-menu.php:775
msgid "Block referrers"
msgstr ""

#: admin/wp-security-firewall-menu.php:778
msgid "Check this to block all referrers recommended by 6G"
msgstr ""

#: admin/wp-security-firewall-menu.php:782
msgid "Block user-agents"
msgstr ""

#: admin/wp-security-firewall-menu.php:785
msgid "Check this to block all user-agents recommended by 6G"
msgstr ""

#: admin/wp-security-firewall-menu.php:789
msgid "Save other settings"
msgstr ""

#: admin/wp-security-firewall-menu.php:823
msgid "The Internet bot settings were successfully saved"
msgstr "De internetbot-instellingen zijn succesvol opgeslagen"

#: admin/wp-security-firewall-menu.php:827
msgid "Internet bot settings"
msgstr "Internetbot instellingen"

#: admin/wp-security-firewall-menu.php:833
msgid "What is an Internet Bot"
msgstr ""

#: admin/wp-security-firewall-menu.php:834
msgid "%s?"
msgstr "%s?"

#: admin/wp-security-firewall-menu.php:836
msgid "A bot is a piece of software which runs on the Internet and performs automatic tasks. For example when Google indexes your pages it uses automatic bots to achieve this task."
msgstr "Een bot is een stukje software dat draait op het internet en dat automatisch taken uitvoert. Bijvoorbeeld wanneer Google uw pagina indexeert wordt gebruik gemaakt van automatische bots."

#: admin/wp-security-firewall-menu.php:837
msgid "A lot of bots are legitimate and non-malicous but not all bots are good and often you will find some which try to impersonate legitimate bots such as \"Googlebot\" but in reality they have nohing to do with Google at all."
msgstr "Veel bots zijn legitiem en niet-kwaadaardig, maar regelmatig komt u er een aantal tegen die proberen om legitieme bots zoals \"Googlebot\" te imiteren. In werkelijkheid hebben ze helemaal niets te maken met Google."

#: admin/wp-security-firewall-menu.php:838
msgid "Although most of the bots out there are relatively harmless sometimes website owners want to have more control over which bots they allow into their site."
msgstr "Hoewel de meeste van de bots relatief onschuldig zijn, willen website-eigenaren soms meer controle hebben over welke bots ze toelaten op hun site."

#: admin/wp-security-firewall-menu.php:839
msgid "This feature allows you to block bots which are impersonating as a Googlebot but actually aren't. (In other words they are fake Google bots)"
msgstr "Met deze functie kunt u bots die zich voordoen als een Googlebot, maar eigenlijk niet zijn, blokkeren."

#: admin/wp-security-firewall-menu.php:840
msgid "Googlebots have a unique indentity which cannot easily be forged and this feature will indentify any fake Google bots and block them from reading your site's pages."
msgstr "Googlebots hebben een unieke identiteit die niet gemakkelijk kan worden vervalst. Deze functie identificeert alle valse Google bots en blokkeert ze bij het lezen van de pagina's van uw site."

#: admin/wp-security-firewall-menu.php:846
msgid "<strong>Attention</strong>: Sometimes non-malicious Internet organizations might have bots which impersonate as a \"Googlebot\"."
msgstr "<strong>Let op:</strong> Soms hebben niet-kwaadaardige internetorganisaties bots die zich kunnen voordoen als een \"Googlebot\"."

#: admin/wp-security-firewall-menu.php:847
msgid "Just be aware that if you activate this feature the plugin will block all bots which use the \"Googlebot\" string in their User Agent information but are NOT officially from Google (irrespective whether they are malicious or not)."
msgstr "Wees u ervan bewust dat als u deze functie activeert alle bots die de \"Googlebot\" string gebruiken in hun User Agent informatie, maar zijn niet officieel van Google zijn (ongeacht of ze schadelijk of niet) zullen worden geblokkeerd."

#: admin/wp-security-firewall-menu.php:848
msgid "All other bots from other organizations such as \"Yahoo\", \"Bing\" etc will not be affected by this feature."
msgstr "Alle andere bots van andere organisaties zoals \"Yahoo\", \"Bing\" etc zullen niet worden beïnvloed door deze functie."

#: admin/wp-security-firewall-menu.php:854
#: admin/wp-security-firewall-menu.php:864
#: classes/grade-system/wp-security-feature-item-manager.php:93
msgid "Block fake Googlebots"
msgstr "Blokkeer namaak Googlebots"

#: admin/wp-security-firewall-menu.php:867
msgid "Check this if you want to block all fake Googlebots."
msgstr "Vink dit aan als je alle nep-Googlebots wil blokkeren."

#: admin/wp-security-firewall-menu.php:871
msgid "This feature will check if the User Agent information of a bot contains the string \"Googlebot\"."
msgstr "Deze functie controleert of de User Agent informatie van een bot de tekst \"Googlebot\" bevat."

#: admin/wp-security-firewall-menu.php:872
msgid "It will then perform a few tests to verify if the bot is legitimately from Google and if so it will allow the bot to proceed."
msgstr "Het zal dan een paar tests uitvoeren om te controleren of de bot rechtmatig van Google is en zo ja, de bot toestaan om verder te gaan."

#: admin/wp-security-firewall-menu.php:873
msgid "If the bot fails the checks then the plugin will mark it as being a fake Googlebot and it will block it"
msgstr "Als de bot niet door de controles komt, zal de plugin deze markeren als een nep Googlebot en de bot blokkeren"

#: admin/wp-security-firewall-menu.php:880
msgid "Save internet bot settings"
msgstr "Internetbot instellingen opslaan"

#: admin/wp-security-firewall-menu.php:916
#: admin/wp-security-firewall-menu.php:938
#: classes/grade-system/wp-security-feature-item-manager.php:95
msgid "Prevent image hotlinking"
msgstr "Voorkom afbeelding hotlinken"

#: admin/wp-security-firewall-menu.php:919
msgid "A Hotlink is where someone displays an image on their site which is actually located on your site by using a direct link to the source of the image on your server."
msgstr "Er is een hotlink wanneer iemand een afbeelding op zijn site weergeeft die op jouw site staat door het toevoegen van een directe link naar de afbeelding op jouw server."

#: admin/wp-security-firewall-menu.php:920
msgid "Due to the fact that the image being displayed on the other person's site is coming from your server, this can cause leaking of bandwidth and resources for you because your server has to present this image for the people viewing it on someone elses's site."
msgstr "Vanwege het feit dat de afbeelding die wordt weergegeven op de site van de andere persoon afkomstig is van uw server, kan dit leiden tot lekken van bandbreedte en bronnen voor u, omdat uw server deze afbeelding moet presenteren voor de mensen die deze op de website van iemand anders bekijken ."

#: admin/wp-security-firewall-menu.php:921
msgid "This feature will prevent people from directly hotlinking images from your site's pages by writing some directives in your .htaccess file."
msgstr "Deze eigenschap zal verhinderen dat mensen direct hotlinking toepassen van afbeelden in de pagina's van uw site, door directives in uw .htaccess-bestand te schrijven."

#: admin/wp-security-firewall-menu.php:926
msgid "Prevent hotlinking"
msgstr "Hotlinken voorkomen"

#: admin/wp-security-firewall-menu.php:941
msgid "Check this if you want to prevent hotlinking to images on your site."
msgstr "Activeer dit als u niet wilt dat afbeeldingen op uw site worden gehotlinked."

#: admin/wp-security-firewall-menu.php:961
msgid "Nonce check failed for delete all 404 event logs operation!"
msgstr "Nonce controle is mislukt voor het verwijderen van alle 404 Event logs!"

#: admin/wp-security-firewall-menu.php:972
msgid "404 Detection Feature - Delete all 404 event logs operation failed!"
msgstr "Eigenschap 404-detectie - Verwijderen van alle 404-gebeurtenissen is mislukt!"

#: admin/wp-security-firewall-menu.php:976
msgid "All 404 event logs were deleted from the DB successfully!"
msgstr "Alle 404-gebeurtenissen werden succesvol uit de DB verwijderd!"

#: admin/wp-security-firewall-menu.php:1000
msgid "You entered a non numeric value for the lockout time length field. It has been set to the default value."
msgstr "U hebt een niet-numerieke waarde opgegeven voor het veld Lengte van vergrendelingstijd. Het is ingesteld op de standaardwaarde."

#: admin/wp-security-firewall-menu.php:1006
msgid "You entered an incorrect format for the \"Redirect URL\" field. It has been set to the default value."
msgstr "U hebt een verkeerd formaat ingevoerd voor het veld \"OmleidingsURL\". Het is ingesteld op de standaardwaarde."

#: admin/wp-security-firewall-menu.php:1039
msgid "404 detection configuration"
msgstr "Configuratie 404-detectie"

#: admin/wp-security-firewall-menu.php:1042
msgid "A 404 or Not Found error occurs when somebody tries to access a non-existent page on your website."
msgstr "Er treedt een 404-of niet-gevonden-fout als iemand probeert een niet-bestaande pagina op uw website te openen."

#: admin/wp-security-firewall-menu.php:1043
msgid "Typically, most 404 errors happen quite innocently when people have mis-typed a URL or used an old link to page which doesn't exist anymore."
msgstr "Meestal gebeuren de meeste 404-fouten vrij onschuldig wanneer mensen een URL verkeerd hebben getypt of een link naar een pagina hebben gebruikt die niet meer bestaat."

#: admin/wp-security-firewall-menu.php:1044
msgid "However, in some cases you may find many repeated 404 errors which occur in a relatively short space of time and from the same IP address which are all attempting to access a variety of non-existent page URLs."
msgstr "In sommige gevallen kunt u echter veel herhaalde 404-fouten vinden die zich in een relatief korte tijdspanne voordoen en van hetzelfde IP-adres die allemaal proberen toegang te krijgen tot een verscheidenheid aan niet-bestaande pagina-URL's."

#: admin/wp-security-firewall-menu.php:1045
msgid "Such behaviour can mean that a hacker might be trying to find a particular page or URL for sinister reasons."
msgstr "Dergelijk gedrag kan betekenen dat een hacker om een duistere reden een bepaalde pagina of URL probeert te vinden ."

#: admin/wp-security-firewall-menu.php:1046
msgid "This feature allows you to monitor all 404 events which occur on your site, and it also gives you the option of blocking IP addresses for a configured length of time."
msgstr "Met deze functie kunt u alle 404-gebeurtenissen monitoren die plaatsvinden op uw website, en het geeft u ook de mogelijkheid om IP-adressen te blokkeren voor een geconfigureerde tijdsduur."

#: admin/wp-security-firewall-menu.php:1047
msgid "If you want to temporarily block or blacklist an IP address, simply click the \"Temp Block\" or \"Blacklist IP\" link for the applicable IP entry in the \"404 Event Logs\" table below."
msgstr "Als u een IP-adres tijdelijk wilt blokkeren of blacklisten, klikt u eenvoudig op de koppeling \"Temp Block \" of \"Blacklist IP\" voor het toepasselijke IP-item in de tabel \"404 Event Logs\" hieronder."

#: admin/wp-security-firewall-menu.php:1071
msgid "404 detection options"
msgstr "Opties 404-detectie"

#: admin/wp-security-firewall-menu.php:1083
msgid "Enable 404 IP detection and lockout"
msgstr "Schakel 404 IP-detectie en vergrendeling in"

#: admin/wp-security-firewall-menu.php:1086
msgid "Check this if you want to enable the lockout of selected IP addresses."
msgstr "Selecteer dit als u de vergrendeling van geselecteerde IP-adressen wilt inschakelen ."

#: admin/wp-security-firewall-menu.php:1091
msgid "When you enable this checkbox, all 404 events on your site will be logged in the table below. You can monitor these events and select some IP addresses listed in the table below and block them for a specified amount of time. All IP addresses you select to be blocked from the \"404 Event Logs\" table section will be unable to access your site during the time specified."
msgstr "Wanneer u dit selectievakje inschakelt, worden alle 404-gebeurtenissen op uw site in de onderstaande tabel vastgelegd. U kunt deze gebeurtenissen controleren en een aantal IP-adressen selecteren in de onderstaande tabel en ze blokkeren voor een bepaalde tijd. Alle IP-adressen die u selecteert om te worden geblokkeerd in het tabelgedeelte \"404 Event Logs\", hebben gedurende de opgegeven tijd geen toegang tot uw site ."

#: admin/wp-security-firewall-menu.php:1099
msgid "Enable 404 event logging"
msgstr "404-logboekregistratie inschakelen"

#: admin/wp-security-firewall-menu.php:1102
msgid "Check this if you want to enable the logging of 404 events"
msgstr "Selecteer dit als u het loggen van 404-gebeurtenissen wilt inschakelen"

#: admin/wp-security-firewall-menu.php:1107
msgid "Time length of 404 lockout (minutes)"
msgstr ""

#: admin/wp-security-firewall-menu.php:1109
msgid "Set the length of time for which a blocked IP address will be prevented from visiting your site"
msgstr "Stel in hoe lang het duurt dat een geblokkeerd IP-adres uw site niet kan bezoeken"

#: admin/wp-security-firewall-menu.php:1114
msgid "You can lock any IP address which is recorded in the \"404 Event Logs\" table section below."
msgstr "U kunt elk IP-adres vergrendelen dat is vastgelegd in het onderstaande tabelgedeelte \"404 Event Logs\"."

#: admin/wp-security-firewall-menu.php:1116
msgid "To temporarily lock an IP address, hover over the ID column and click the \"Temp Block\" link for the applicable IP entry."
msgstr "Om tijdelijk een IP-adres te vergrendelen, plaatst u de muisaanwijzer op de kolom ID en klikt u op de koppeling \"Tijdelijk blokkeren \" voor het van toepassing zijnde IP-item."

#: admin/wp-security-firewall-menu.php:1123
msgid "404 lockout redirect URL"
msgstr "404-vergrendeling voor redirectie URL"

#: admin/wp-security-firewall-menu.php:1125
msgid "A blocked visitor will be automatically redirected to this URL."
msgstr "Een geblokkeerde bezoeker wordt automatisch doorgestuurd naar deze URL."

#: admin/wp-security-firewall-menu.php:1135
msgid "This list displays the 404 event logs when somebody tries to access a non-existent page on your website."
msgstr ""

#: admin/wp-security-firewall-menu.php:1136
msgid "404 event logs that are older than %1$d days are purged automatically."
msgstr ""

#: admin/wp-security-firewall-menu.php:1141
msgid "404 event logs"
msgstr "404-logs"

#: admin/wp-security-firewall-menu.php:1163
#: admin/wp-security-firewall-menu.php:1172
#: admin/wp-security-user-login-menu.php:495
#: admin/wp-security-user-login-menu.php:504
#: admin/wp-security-user-login-menu.php:653
#: admin/wp-security-user-login-menu.php:662
msgid "Export to CSV"
msgstr "Exporteer naar CSV"

#: admin/wp-security-firewall-menu.php:1169
#: admin/wp-security-user-login-menu.php:501
#: admin/wp-security-user-login-menu.php:659
msgid "Click this button if you wish to download this log in CSV format."
msgstr "Klik op deze knop als u dit log wilt downloaden in CSV-formaat."

#: admin/wp-security-firewall-menu.php:1176
#: admin/wp-security-firewall-menu.php:1185
msgid "Delete all 404 event logs"
msgstr "Verwijder alle logbestanden van 404-evenementen"

#: admin/wp-security-firewall-menu.php:1182
msgid "Click this button if you wish to purge all 404 event logs from the DB."
msgstr "Klik op deze knop als u alle 404-eventlogs wilt verwijderen uit de DB."

#: admin/wp-security-firewall-menu.php:1241
msgid "Custom .htaccess rules settings"
msgstr "Aangepaste instellingen voor .htaccessregels"

#: admin/wp-security-firewall-menu.php:1248
msgid "This feature can be used to apply your own custom .htaccess rules and directives."
msgstr "Deze functie kan worden gebruikt om uw eigen aangepaste .htaccess-regels en -richtlijnen toe te passen."

#: admin/wp-security-firewall-menu.php:1249
msgid "It is useful for when you want to tweak our existing firewall rules or when you want to add your own."
msgstr "Dit is handig als u onze bestaande firewall-regels wilt aanpassen of als u uw eigen firewallregels wilt toevoegen."

#: admin/wp-security-firewall-menu.php:1250
msgid "NOTE: This feature can only be used if your site is hosted in an apache or similar web server."
msgstr ""

#: admin/wp-security-firewall-menu.php:1256
msgid "<strong>Warning</strong>: Only use this feature if you know what you are doing."
msgstr "<strong>Waarschuwing</strong>: Gebruik deze functie alleen als u weet wat u doet."

#: admin/wp-security-firewall-menu.php:1257
msgid "Incorrect .htaccess rules or directives can break or prevent access to your site."
msgstr "Onjuiste .htaccess-regels of -richtlijnen kunnen de toegang tot uw site verbreken of verhinderen ."

#: admin/wp-security-firewall-menu.php:1258
msgid "It is your responsibility to ensure that you are entering the correct code!"
msgstr "Het is uw verantwoordelijkheid om ervoor te zorgen dat u de juiste code invoert!"

#: admin/wp-security-firewall-menu.php:1259
msgid "If you break your site you will need to access your server via FTP or something similar and then edit your .htaccess file and delete the changes you made."
msgstr "Als u de werking van de website uitschakeld hebt u toegang nodig tot uw site via FTP of iets dergelijks en bewerk vervolgens je het .htaccess-bestand en verwijder de wijzigingen die je gemaakt hebt."

#: admin/wp-security-firewall-menu.php:1265
msgid "Custom .htaccess rules"
msgstr "Aangepaste .htaccess-regels"

#: admin/wp-security-firewall-menu.php:1269
msgid "Enable custom .htaccess rules"
msgstr "Aangepaste .htaccess-regels gebruiken"

#: admin/wp-security-firewall-menu.php:1272
msgid "Check this if you want to enable custom rules entered in the text box below"
msgstr "Selecteer dit als u aangepaste regels wilt inschakelen die zijn ingevoerd in het onderstaande tekstvak"

#: admin/wp-security-firewall-menu.php:1276
msgid "Place custom rules at the top"
msgstr "Plaatst eigen regels bovenaan"

#: admin/wp-security-firewall-menu.php:1279
msgid "Check this if you want to place your custom rules at the beginning of all the rules applied by this plugin"
msgstr "Selecteer dit als u uw eigen regels aan het begin van alle regels wilt plaatsen die door deze plugin worden toegepast"

#: admin/wp-security-firewall-menu.php:1283
msgid "Enter custom .htaccess rules:"
msgstr "Vul aangepaste .htaccess-regels in:"

#: admin/wp-security-firewall-menu.php:1287
msgid "Enter your custom .htaccess rules/directives."
msgstr "Vul jouw eigen .htaccess-regels in."

#: admin/wp-security-firewall-menu.php:1292
msgid "Save custom rules"
msgstr "Aangepaste regels opslaan"

#: admin/wp-security-firewall-setup-notice.php:338
#: admin/wp-security-firewall-setup-notice.php:407
#: admin/wp-security-firewall-setup-notice.php:479
#: admin/wp-security-firewall-setup-notice.php:595
#: wp-security.php:43
msgid "All In One WP Security and Firewall"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:340
msgid "We were unable to create the file necessary to give you the highest level of protection."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:341
msgid "Your firewall will have reduced protection which means some of your firewall's functionality will be unavailable."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:342
msgid "If you would like to manually set up the necessary file, please follow these steps:"
msgstr ""

#. translators: %s Boostrap file name.
#. translators: %s Firewall file name.
#: admin/wp-security-firewall-setup-notice.php:346
#: admin/wp-security-firewall-setup-notice.php:453
msgid "1. Create a file with the name %s in the same directory as your WordPress install is in, i.e.:"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:350
msgid "2. Paste in the following code:"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:352
#: admin/wp-security-firewall-setup-notice.php:462
msgid "3. Save the file and press the 'Try again' button below:"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:372
msgid "1. Open the following file:"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:378
msgid "2. Look for the auto_prepend_file directive."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:382
msgid "2. Look for the following:"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:388
msgid "3. Change it to the following:"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:392
msgid "4. Save the file  and press the 'Try again' button below:"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:392
#: admin/wp-security-firewall-setup-notice.php:441
msgid "You may have to wait up to 5 minutes before the settings take effect."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:410
msgid "Your firewall has been installed with the highest level of protection."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:411
msgid "You may have to wait 5 minutes for the changes to take effect."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:434
msgid "1. Open your php.ini file."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:437
msgid "2. Set the auto_prepend_file directive like below:"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:441
msgid "3. Restart the webserver and refresh the page"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:458
msgid "2. Paste in the following directives:"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:482
msgid "We were unable to set up your firewall with the highest level of protection."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:483
msgid "Your firewall will have reduced functionality."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:487
msgid "To give your site the highest level of protection, please follow these steps:"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:500
msgid "Note: if you're unable to perform any of the aforementioned steps, please ask your web hosting provider for further assistance."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:517
msgid "Try again"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:539
msgid "We have detected that your AIOS firewall is not fully installed, and therefore does not have the highest level of protection. "
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:540
msgid "Your firewall will have reduced functionality until it has been upgraded. "
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:542
msgid "Upgrade your protection now"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:598
msgid "Our PHP-based firewall has been created to give you even greater protection."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:602
msgid "If you already have our .htaccess-based firewall enabled, you will still need to set up the PHP-based firewall to benefit from its protection."
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:605
msgid "To set up the PHP-based firewall, press the 'Set up now' button below:"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:608
msgid "Set up now"
msgstr ""

#: admin/wp-security-firewall-setup-notice.php:614
#: templates/notices/custom-notice.php:10
#: templates/notices/custom-notice.php:12
#: templates/notices/horizontal-notice.php:50
#: templates/notices/horizontal-notice.php:52
#: templates/notices/htaccess-to-php-feature-notice.php:10
#: templates/notices/htaccess-to-php-feature-notice.php:12
msgid "Dismiss"
msgstr ""

#: admin/wp-security-list-404.php:91
msgid "Event type"
msgstr ""

#: admin/wp-security-list-404.php:92
#: admin/wp-security-list-logged-in-users.php:46
#: admin/wp-security-list-registered-users.php:74
msgid "IP address"
msgstr ""

#: admin/wp-security-list-404.php:93
msgid "Attempted URL"
msgstr ""

#: admin/wp-security-list-404.php:94
msgid "Referer"
msgstr ""

#: admin/wp-security-list-404.php:96
msgid "Lock status"
msgstr ""

#: admin/wp-security-list-404.php:118
msgid "Temp block IP"
msgstr ""

#: admin/wp-security-list-404.php:119
msgid "Blacklist IP"
msgstr ""

#: admin/wp-security-list-404.php:120
#: admin/wp-security-list-acct-activity.php:82
#: admin/wp-security-list-locked-ip.php:37
#: admin/wp-security-list-locked-ip.php:84
#: admin/wp-security-list-login-fails.php:73
#: admin/wp-security-list-registered-users.php:93
msgid "Delete"
msgstr ""

#: admin/wp-security-list-404.php:128
#: admin/wp-security-list-404.php:136
#: admin/wp-security-list-404.php:143
#: admin/wp-security-list-acct-activity.php:92
#: admin/wp-security-list-comment-spammer-ip.php:95
#: admin/wp-security-list-locked-ip.php:97
#: admin/wp-security-list-locked-ip.php:105
#: admin/wp-security-list-login-fails.php:85
#: admin/wp-security-list-permanent-blocked-ip.php:96
#: admin/wp-security-list-registered-users.php:107
#: admin/wp-security-list-registered-users.php:115
#: admin/wp-security-list-registered-users.php:123
msgid "Please select some records using the checkboxes"
msgstr "Selecteer s.v.p. een aantal records met behulp van de selectievakjes"

#: admin/wp-security-list-404.php:278
msgid "Nonce check failed for delete selected 404 event logs operation!"
msgstr "Controle nonce is mislukt voor het verwijderen van de geselecteerde 404-eventlogs!"

#: admin/wp-security-list-acct-activity.php:35
msgid "Are you sure you want to delete this item?"
msgstr ""

#: admin/wp-security-list-acct-activity.php:46
msgid "Login session still active"
msgstr ""

#: admin/wp-security-list-acct-activity.php:60
#: admin/wp-security-list-locked-ip.php:60
#: admin/wp-security-list-logged-in-users.php:44
#: admin/wp-security-list-login-fails.php:54
#: admin/wp-security-list-registered-users.php:69
msgid "User ID"
msgstr ""

#: admin/wp-security-list-acct-activity.php:61
#: admin/wp-security-list-locked-ip.php:61
#: admin/wp-security-list-login-fails.php:55
msgid "Username"
msgstr "Gebruikersnaam"

#: admin/wp-security-list-acct-activity.php:62
msgid "Login date"
msgstr ""

#: admin/wp-security-list-acct-activity.php:63
msgid "Logout date"
msgstr ""

#: admin/wp-security-list-acct-activity.php:136
msgid "Nonce check failed for delete selected account activity logs operation!"
msgstr "Nonce controle is mislukt voor het verwijderen van de geselecteerde logboeken van accountactiviteit !"

#: admin/wp-security-list-comment-spammer-ip.php:59
msgid "Spammer IP"
msgstr ""

#: admin/wp-security-list-comment-spammer-ip.php:60
msgid "Number of spam comments from this IP"
msgstr ""

#: admin/wp-security-list-comment-spammer-ip.php:61
msgid "Status"
msgstr ""

#: admin/wp-security-list-comment-spammer-ip.php:81
msgid "Block"
msgstr ""

#: admin/wp-security-list-comment-spammer-ip.php:130
#: admin/wp-security-list-comment-spammer-ip.php:179
msgid "Nonce check failed for delete selected blocked IP operation!"
msgstr "Nonce controle voor het verwijderen van geselecteerde geblokkeerde IP's is mislukt!"

#: admin/wp-security-list-comment-spammer-ip.php:137
msgid "The selected IP addresses are now permanently blocked!"
msgstr "De geselecteerde IP-adressen zijn nu permanent geblokkeerd !"

#: admin/wp-security-list-comment-spammer-ip.php:193
msgid "The selected IP addresses were saved in the blacklist configuration settings."
msgstr "De geselecteerde IP-adressen zijn opgeslagen in de configuratie-instellingen van de zwarte lijst."

#: admin/wp-security-list-comment-spammer-ip.php:201
msgid "The .htaccess file was successfully modified to include the selected IP addresses."
msgstr "Het .htaccess-bestand is met succes gewijzigd om de geselecteerde IP-adressen op te nemen."

#: admin/wp-security-list-comment-spammer-ip.php:212
msgid "NOTE: The .htaccess file was not modified because you have disabled the \"Enable IP or User Agent Blacklisting\" check box."
msgstr "LET OP: Het .htaccess-bestand is niet gewijzigd, omdat je de \"Enable IP of User Agent zwarte lijst\" checkbox hebt uitgeschakeld."

#: admin/wp-security-list-comment-spammer-ip.php:213
msgid "To block these IP addresses you will need to enable the above flag in the %s menu"
msgstr "Om deze IP-adressen te blokkeren moet u de bovenstaande vlag in het enable%s menu activeren"

#: admin/wp-security-list-debug.php:47
msgid "Level"
msgstr ""

#: admin/wp-security-list-debug.php:48
msgid "Message"
msgstr ""

#: admin/wp-security-list-debug.php:49
msgid "Type"
msgstr ""

#: admin/wp-security-list-locked-ip.php:36
#: admin/wp-security-list-locked-ip.php:83
msgid "Unlock"
msgstr ""

#: admin/wp-security-list-locked-ip.php:59
msgid "Locked IP/range"
msgstr ""

#: admin/wp-security-list-locked-ip.php:62
#: admin/wp-security-list-permanent-blocked-ip.php:67
msgid "Reason"
msgstr ""

#: admin/wp-security-list-locked-ip.php:63
msgid "Date locked"
msgstr ""

#: admin/wp-security-list-locked-ip.php:64
msgid "Release date"
msgstr ""

#: admin/wp-security-list-locked-ip.php:134
msgid "The selected IP entries were unlocked successfully."
msgstr "De geselecteerde IP-vermeldingen zijn succesvol ontgrendeld."

#: admin/wp-security-list-locked-ip.php:140
msgid "Nonce check failed for unlock IP operation!"
msgstr "Nonce check mislukt voor ontgrendeling IP-werking!"

#: admin/wp-security-list-locked-ip.php:147
msgid "The selected IP entry was unlocked successfully."
msgstr "Het geselecteerde IP-item is succesvol ontgrendeld!"

#: admin/wp-security-list-logged-in-users.php:45
#: admin/wp-security-list-registered-users.php:70
msgid "Login name"
msgstr ""

#: admin/wp-security-list-logged-in-users.php:87
msgid "Nonce check failed for force user logout operation!"
msgstr "Controle nonce mislukt voor gedwongen afmelding van de gebruiker!"

#: admin/wp-security-list-logged-in-users.php:96
msgid "The selected user was logged out successfully!"
msgstr "De geselecteerde gebruiker is succesvol uitgelogd!"

#: admin/wp-security-list-login-fails.php:53
msgid "Login IP range"
msgstr ""

#: admin/wp-security-list-login-fails.php:130
msgid "Nonce check failed for delete failed login record operation!"
msgstr "Controle nonce is mislukt voor verwijderen mislukt inloggen bewerking!"

#: admin/wp-security-list-permanent-blocked-ip.php:66
msgid "Blocked IP"
msgstr ""

#: admin/wp-security-list-permanent-blocked-ip.php:87
msgid "Unblock"
msgstr ""

#: admin/wp-security-list-permanent-blocked-ip.php:122
#: admin/wp-security-list-permanent-blocked-ip.php:139
msgid "Successfully unblocked and deleted the selected record(s)."
msgstr ""

#: admin/wp-security-list-permanent-blocked-ip.php:126
#: admin/wp-security-list-permanent-blocked-ip.php:143
msgid "Failed to unblock and delete the selected record(s)."
msgstr ""

#: admin/wp-security-list-permanent-blocked-ip.php:133
msgid "Nonce check failed for unblock IP operation!"
msgstr "Nonce check mislukt voor deblokkering IP-bewerking!"

#: admin/wp-security-list-registered-users.php:71
msgid "Email"
msgstr "E-mail"

#: admin/wp-security-list-registered-users.php:72
msgid "Register date"
msgstr ""

#: admin/wp-security-list-registered-users.php:73
msgid "Account status"
msgstr ""

#: admin/wp-security-list-registered-users.php:92
msgid "Approve"
msgstr ""

#: admin/wp-security-list-registered-users.php:94
msgid "Block IP"
msgstr ""

#: admin/wp-security-list-registered-users.php:159
msgid "The selected accounts were approved successfully!"
msgstr "De geselecteerd accounts zijn succesvol geaccepteerd!"

#: admin/wp-security-list-registered-users.php:163
msgid "The following accounts failed to update successfully: "
msgstr "De volgende accounts konden niet succesvol worden bijgewerkt: "

#: admin/wp-security-list-registered-users.php:171
msgid "The selected account was approved successfully!"
msgstr "Het geselecteerde account is succesvol goedgekeurd !"

#: admin/wp-security-list-registered-users.php:190
msgid "Your account is now active"
msgstr "Jouw account is nu actief"

#: admin/wp-security-list-registered-users.php:191
msgid "Your account with username: "
msgstr "Jouw account met gebruikersnaam: "

#: admin/wp-security-list-registered-users.php:191
msgid " is now active"
msgstr " is nu actief"

#: admin/wp-security-list-registered-users.php:222
msgid "The selected accounts were deleted successfully!"
msgstr "De geselecteerde accounts zijn succesvol verwijderd!"

#: admin/wp-security-list-registered-users.php:230
msgid "Nonce check failed for delete registered user account operation!"
msgstr "Nonce check mislukt voor verwijderen van geregistreerde gebruikersaccount!"

#: admin/wp-security-list-registered-users.php:238
msgid "The selected account was deleted successfully!"
msgstr "Het geselecteerde account is succesvol verwijderd!"

#: admin/wp-security-list-registered-users.php:264
msgid "The selected IP addresses were successfully added to the permanent block list!"
msgstr "De geselecteerde IP-adressen zijn met succes toegevoegd aan de permanente blokkeerlijst !"

#: admin/wp-security-list-registered-users.php:265
#: admin/wp-security-list-registered-users.php:282
msgid "View Blocked IPs"
msgstr "Bekijk geblokkeerde IP's"

#: admin/wp-security-list-registered-users.php:274
msgid "Nonce check failed for block IP operation of registered user!"
msgstr "Nonce-controle mislukt voor blok IP-bewerking van geregistreerde gebruiker!"

#: admin/wp-security-list-registered-users.php:281
msgid "The selected IP was successfully added to the permanent block list!"
msgstr "De geselecteerde IP is met succes toegevoegd aan de permanente blokkeerlijst !"

#: admin/wp-security-maintenance-menu.php:25
msgid "Visitor lockout"
msgstr "Vergrendeling van bezoekers"

#: admin/wp-security-maintenance-menu.php:85
msgid "Site lockout feature settings saved!"
msgstr "Locatie lockout-functie-instellingen opgeslagen!"

#: admin/wp-security-maintenance-menu.php:92
msgid "General visitor lockout"
msgstr "Algemene bezoekersblokkering"

#: admin/wp-security-maintenance-menu.php:98
msgid "This feature allows you to put your site into \"maintenance mode\" by locking down the front-end to all visitors except logged in users with super admin privileges."
msgstr "Met deze functie kunt u uw website in de \"maintenance mode\" zetten door het vergrendelen van de front-end voor alle bezoekers, behalve voor ingelogde gebruikers met superadmin-rechten."

#: admin/wp-security-maintenance-menu.php:99
msgid "Locking your site down to general visitors can be useful if you are investigating some issues on your site or perhaps you might be doing some maintenance and wish to keep out all traffic for security reasons."
msgstr "Vergrendelen van uw website voor algemene bezoekers kan handig zijn als je een aantal zaken op je website onderzoekt of misschien om onderhoud te doen en je alle verkeer om veiligheidsredenen wilt blokkeren."

#: admin/wp-security-maintenance-menu.php:104
msgid "Enable front-end lockout"
msgstr "Front-end lockout inschakelen"

#: admin/wp-security-maintenance-menu.php:107
msgid "Check this if you want all visitors except those who are logged in as administrator to be locked out of the front-end of your site."
msgstr "Vink dit aan als u wilt dat alle bezoekers, behalve degenen die zijn aangemeld als beheerder, worden uitgesloten van de front-end van uw site ."

#: admin/wp-security-maintenance-menu.php:111
msgid "Enter a message:"
msgstr "Vul een bericht in:"

#: admin/wp-security-maintenance-menu.php:123
msgid "Enter a message you wish to display to visitors when your site is in maintenance mode."
msgstr "Voer een bericht in dat u wilt weergeven aan bezoekers wanneer uw site in onderhoudsmodus is."

#: admin/wp-security-maintenance-menu.php:130
msgid "Save site lockout settings"
msgstr "Opslaan Site-lockout-instellingen"

#: admin/wp-security-misc-options-menu.php:28
msgid "Copy protection"
msgstr "Kopieerbescherming"

#: admin/wp-security-misc-options-menu.php:29
msgid "Frames"
msgstr "Frames"

#: admin/wp-security-misc-options-menu.php:30
msgid "Users enumeration"
msgstr "Gebruikersopsomming"

#: admin/wp-security-misc-options-menu.php:31
msgid "WP REST API"
msgstr "WP REST API"

#: admin/wp-security-misc-options-menu.php:89
msgid "Copy Protection feature settings saved!"
msgstr "Instellingen functie Kopieerbeveiliging opgeslagen!"

#: admin/wp-security-misc-options-menu.php:94
msgid "Disable the ability to copy text"
msgstr "Tekst kopiëren uitschakelen"

#: admin/wp-security-misc-options-menu.php:100
msgid "This feature allows you to disable the ability to select and copy text from your front end."
msgstr "Met deze functie kunt u de mogelijkheid uitschakelen om tekst van uw frontend te selecteren en te kopiëren ."

#: admin/wp-security-misc-options-menu.php:101
msgid "When admin user is logged in, the feature is automatically disabled for his session."
msgstr "Wanneer de admin-gebruiker is aangemeld, wordt de functie automatisch uitgeschakeld voor zijn sessie."

#: admin/wp-security-misc-options-menu.php:106
msgid "Enable copy protection"
msgstr "Kopieerbescherming gebruiken"

#: admin/wp-security-misc-options-menu.php:109
msgid "Check this if you want to disable the \"Right click\", \"Text selection\" and \"Copy\" option on the front end of your site."
msgstr "Schakel dit selectievakje in als u de optie 'Rechtsklikken', 'Tekstselectie' en 'Kopiëren' aan de voorkant van uw site wilt uitschakelen ."

#: admin/wp-security-misc-options-menu.php:116
msgid "Save copy protection settings"
msgstr "Bewaar kopieerbeveiligingsinstellingen"

#: admin/wp-security-misc-options-menu.php:140
msgid "Frame Display Prevention feature settings saved!"
msgstr "Instellingen functie Frame-displaypreventie opgeslagen!"

#: admin/wp-security-misc-options-menu.php:145
msgid "Prevent your site from being displayed in a frame"
msgstr "Voorkom dat uw site in een frame wordt weergegeven"

#: admin/wp-security-misc-options-menu.php:151
msgid "This feature allows you to prevent other sites from displaying any of your content via a frame or iframe."
msgstr "Met deze functie kunt u voorkomen dat andere websites inhoud van uw site via een frame of iframe tonen."

#: admin/wp-security-misc-options-menu.php:152
msgid "When enabled, this feature will set the \"X-Frame-Options\" paramater to \"sameorigin\" in the HTTP header."
msgstr "Als deze functie is ingeschakeld, wordt de parameter 'X-frame-opties' ingesteld op 'sameorigin' in de HTTP-header ."

#: admin/wp-security-misc-options-menu.php:157
msgid "Enable iFrame protection"
msgstr "Gebruik iFrame-bescherming"

#: admin/wp-security-misc-options-menu.php:160
msgid "Check this if you want to stop other sites from displaying your content in a frame or iframe."
msgstr "Selecteer dit als u andere websites wilt verhinderen inhoud in een frame of iframe weer te geven."

#: admin/wp-security-misc-options-menu.php:191
msgid "Users Enumeration Prevention feature settings saved!"
msgstr "Gebruikersopsomming preventiefunctie-instellingen opgeslagen!"

#: admin/wp-security-misc-options-menu.php:196
msgid "Prevent users enumeration"
msgstr "Voorkom gebruikersopsomming"

#: admin/wp-security-misc-options-menu.php:202
msgid "This feature allows you to prevent external users/bots from fetching the user info with urls like \"/?author=1\"."
msgstr "Met deze functie kunt  u voorkomen dat externe gebruikers / bots de gebruikersinformatie ophalen met urls zoals \"/? Author = 1\"."

#: admin/wp-security-misc-options-menu.php:203
msgid "When enabled, this feature will print a \"forbidden\" error rather than the user information."
msgstr "Als deze functie is ingeschakeld, drukt deze een 'verboden' fout af in plaats van de gebruikers informatie."

#: admin/wp-security-misc-options-menu.php:208
msgid "Disable users enumeration"
msgstr "Gebruikersopsomming uitschakelen"

#: admin/wp-security-misc-options-menu.php:211
msgid "Check this if you want to stop users enumeration."
msgstr "Vink dit aan als u de opsomming van gebruikers wilt stoppen."

#: admin/wp-security-misc-options-menu.php:242
msgid "WP REST API Security feature settings saved!"
msgstr "WP REST API beveiligingsfunctie-instellingen opgeslagen!"

#: admin/wp-security-misc-options-menu.php:253
msgid "This feature allows you to block WordPress REST API access for unauthorized requests."
msgstr "Deze functie maakt het mogelijk om de WordPress REST API te blokkeren voor toegang tot ongeautoriseerde verzoeken."

#: admin/wp-security-misc-options-menu.php:254
msgid "When enabled this feature will only allow REST requests to be processed if the user is logged in."
msgstr "Indien ingeschakeld, staat deze functie alleen toe dat REST-aanvragen worden verwerkt als de gebruiker is aangemeld."

#: admin/wp-security-misc-options-menu.php:260
msgid "Beware that if you are using other plugins which have registered REST endpoints (eg, Contact Form 7), then this feature will also block REST requests used by these plugins if the user is not logged in. It is recommended that you leave this feature disabled if you want uninterrupted functionality for such plugins."
msgstr "Wees ervan bewust dat als u andere plugins gebruikt die geregistreerde REST eindpunten hebben (b.v., Contact Form 7) , dan zal deze eigenschap ook REST-verzoeken die door deze plugins worden gebruikt blokkeren als de gebruiker niet ingelogd is. Het wordt aanbevolen dat u deze functie uitgeschakeld laat als u ononderbroken functionaliteit voor dergelijke plugins wilt hebben."

#: admin/wp-security-misc-options-menu.php:268
msgid "Disallow unauthorized REST requests"
msgstr "Geen ongeautoriseerde REST-aanvragen toestaan"

#: admin/wp-security-misc-options-menu.php:271
msgid "Check this if you want to stop REST API access for non-logged in requests."
msgstr "Selecteer dit als u de REST API-toegang wilt stoppen voor niet-ingelogde verzoeken."

#: admin/wp-security-settings-menu.php:25
msgid "General settings"
msgstr "Algemene instellingen"

#: admin/wp-security-settings-menu.php:29
#: admin/wp-security-settings-menu.php:33
msgid "file"
msgstr "Bestand"

#: admin/wp-security-settings-menu.php:37
msgid "Delete plugin settings"
msgstr ""

#: admin/wp-security-settings-menu.php:41
msgid "WP version info"
msgstr "WP-versie-info"

#: admin/wp-security-settings-menu.php:45
msgid "Import/Export"
msgstr "Import/Export"

#: admin/wp-security-settings-menu.php:52
msgid "Advanced settings"
msgstr "Geavanceerde instellingen"

#: admin/wp-security-settings-menu.php:128
msgid "All the security features have been disabled successfully!"
msgstr "Alle beveiligingsfuncties zijn met succes uitgeschakeld!"

#: admin/wp-security-settings-menu.php:132
#: admin/wp-security-settings-menu.php:159
msgid "Could not write to the .htaccess file. Please restore your .htaccess file manually using the restore functionality in the \".htaccess File\"."
msgstr "Kon het .htaccess-bestand niet schrijven. Herstel uw .htaccess-bestand handmatig met behulp van de herstelfunctionaliteit in het \".htaccess-bestand\"."

#: admin/wp-security-settings-menu.php:137
msgid "Could not write to the wp-config.php. Please restore your wp-config.php file manually using the restore functionality in the \"wp-config.php File\"."
msgstr "Kon niet naar de wp-config.php schrijven. Herstel uw wp-config.php-bestand handmatig met behulp van de herstelfunctionaliteit in het \"wp-config.php-bestand\"."

#: admin/wp-security-settings-menu.php:155
msgid "All firewall rules have been disabled successfully!"
msgstr "Alle firewall-regels zijn succesvol uitgeschakeld!"

#: admin/wp-security-settings-menu.php:177
msgid "Deletion of aio_wp_security_configs option and .htaccess directives failed."
msgstr ""

#: admin/wp-security-settings-menu.php:179
msgid "Reset of aio_wp_security_configs option failed."
msgstr ""

#: admin/wp-security-settings-menu.php:181
msgid "Deletion of .htaccess directives failed."
msgstr ""

#: admin/wp-security-settings-menu.php:183
msgid "All settings have been successfully reset."
msgstr ""

#: admin/wp-security-settings-menu.php:203
msgid "For information, updates and documentation, please visit the"
msgstr ""

#: admin/wp-security-settings-menu.php:203
msgid "Page"
msgstr ""

#: admin/wp-security-settings-menu.php:204
msgid "Follow us"
msgstr ""

#: admin/wp-security-settings-menu.php:204
msgid "on Twitter, Google+ or via Email to stay up to date about the new security features of this plugin."
msgstr ""

#: admin/wp-security-settings-menu.php:208
msgid "WP Security plugin"
msgstr "WP Beveiligingsplugin"

#: admin/wp-security-settings-menu.php:212
msgid "Thank you for using the AIOS security plugin."
msgstr ""

#: admin/wp-security-settings-menu.php:216
msgid "There are a lot of security features in this plugin."
msgstr ""

#: admin/wp-security-settings-menu.php:221
msgid "To start, go through each security option and enable the \"basic\" options."
msgstr ""

#: admin/wp-security-settings-menu.php:225
msgid "The more features you enable, the more security points you will achieve."
msgstr ""

#: admin/wp-security-settings-menu.php:228
msgid "Before doing anything we advise taking a backup of your .htaccess file, database and wp-config.php."
msgstr ""

#: admin/wp-security-settings-menu.php:231
msgid "Backup your database"
msgstr "Maak een back-up van je database"

#: admin/wp-security-settings-menu.php:232
#: admin/wp-security-settings-menu.php:433
msgid "Backup .htaccess file"
msgstr "Maak een back-up van je .htaccess-bestand"

#: admin/wp-security-settings-menu.php:233
#: admin/wp-security-settings-menu.php:534
msgid "Backup wp-config.php file"
msgstr "Maak een back-up van je wp-config.php-bestand"

#: admin/wp-security-settings-menu.php:240
msgid "Disable security features"
msgstr "Veiligheidsopties uitzetten"

#: admin/wp-security-settings-menu.php:246
msgid "If you think that some plugin functionality on your site is broken due to a security feature you enabled in this plugin, then use the following option to turn off all the security features of this plugin."
msgstr "Als u denkt dat sommige plug- in functionaliteit op uw site is verbroken vanwege een beveiligingsfunctie die u in deze plug- in hebt ingeschakeld, gebruikt u de volgende optie om alle beveiligingsfuncties van deze plug-in uit te schakelen ."

#: admin/wp-security-settings-menu.php:250
msgid "Disable all security features"
msgstr "Alle veiligheidsopties uitzetten"

#: admin/wp-security-settings-menu.php:257
#: admin/wp-security-settings-menu.php:267
msgid "Disable all firewall rules"
msgstr "Alle firewall-regels uitzetten"

#: admin/wp-security-settings-menu.php:263
msgid "This feature will disable all firewall rules which are currently active in this plugin and it will also delete these rules from your .htacess file. Use it if you think one of the firewall rules is causing an issue on your site."
msgstr "Met deze functie worden alle firewall-regels uitgeschakeld die momenteel actief zijn in deze plug-in en deze regels worden ook verwijderd uit uw .htacess-bestand. Gebruik het als u denkt dat een van de firewallregels een probleem op uw site veroorzaakt ."

#: admin/wp-security-settings-menu.php:274
#: admin/wp-security-settings-menu.php:287
msgid "Reset settings"
msgstr ""

#: admin/wp-security-settings-menu.php:279
msgid "This button click will delete all of your settings related to the All In One WP Security & Firewall Plugin."
msgstr ""

#: admin/wp-security-settings-menu.php:280
msgid "This button click will reset/empty all the database tables of the security plugin also."
msgstr ""

#: admin/wp-security-settings-menu.php:281
msgid "Use this plugin if you were locked out by the All In One WP Security & Firewall Plugin and/or you are having issues logging in when that plugin is activated."
msgstr ""

#: admin/wp-security-settings-menu.php:282
msgid "In addition to the settings it will also delete any directives which were added to the .htaccess file by the All In One WP Security & Firewall Plugin."
msgstr ""

#: admin/wp-security-settings-menu.php:283
msgid "%1$sNOTE: %2$sAfter deleting the settings you will need to re-configure the All In One WP Security & Firewall Plugin."
msgstr ""

#: admin/wp-security-settings-menu.php:295
msgid "Debug settings"
msgstr "Debu- instellingen"

#: admin/wp-security-settings-menu.php:301
msgid "This setting allows you to enable/disable debug for this plugin."
msgstr "Met deze instelling kunt u foutopsporing voor deze plug-in in- of uitschakelen ."

#: admin/wp-security-settings-menu.php:307
msgid "Enable debug"
msgstr "Schakel debug in"

#: admin/wp-security-settings-menu.php:310
msgid "Check this if you want to enable debug. You should keep this option disabled after you have finished debugging the issue."
msgstr "Vink dit aan als u debug wilt inschakelen. U moet deze optie uitgeschakeld houden nadat u klaar bent met het debuggen van het probleem."

#: admin/wp-security-settings-menu.php:314
msgid "Save debug settings"
msgstr "Sla debug-instellingen op"

#: admin/wp-security-settings-menu.php:350
msgid "Your .htaccess file was successfully backed up! Using an FTP program go to the \"/wp-content/aiowps_backups\" directory to save a copy of the file to your computer."
msgstr "Er is een back-up van uw .htaccess-bestand gemaakt! Ga met behulp van een FTP-programma naar de map \"/wp-content/aiowps_backups\" om een kopie van het bestand op uw computer op te slaan ."

#: admin/wp-security-settings-menu.php:356
msgid "htaccess file rename failed during backup. Please check your root directory for the backup file using FTP."
msgstr "Hernoemen .htaccess-bestand is mislukt tijdens back-up. Controleer de hoofdmap voor het back-upbestand met behulp van FTP."

#: admin/wp-security-settings-menu.php:362
msgid "htaccess backup failed."
msgstr "htaccess-back-up mislukt."

#: admin/wp-security-settings-menu.php:377
msgid "Please choose a .htaccess to restore from."
msgstr "Kies alstublieft een .htaccess-bestand om terug te plaatsen."

#: admin/wp-security-settings-menu.php:392
msgid "htaccess file restore failed. Please attempt to restore the .htaccess manually using FTP."
msgstr ".htaccess-bestand herstellen mislukt. Probeer de .htaccess handmatig te herstellen met behulp van FTP."

#: admin/wp-security-settings-menu.php:396
msgid "Your .htaccess file has successfully been restored!"
msgstr "Uw .htaccess-bestand is succesvol hersteld!"

#: admin/wp-security-settings-menu.php:402
msgid "htaccess Restore operation failed! Please check the contents of the file you are trying to restore from."
msgstr ".htaccess-herstelbewerking mislukt! Controleer de inhoud van het bestand dat u probeert te herstellen."

#: admin/wp-security-settings-menu.php:408
msgid ".htaccess file operations"
msgstr ".htaccess bestandsbewerkingen"

#: admin/wp-security-settings-menu.php:411
msgid "Your \".htaccess\" file is a key component of your website's security and it can be modified to implement various levels of protection mechanisms."
msgstr "Uw \".htaccess\"-bestand is een belangrijk onderdeel van de beveiliging van uw website en het kan worden gewijzigd om verschillende niveaus van beveiligingsmechanismen te implementeren."

#: admin/wp-security-settings-menu.php:412
msgid "This feature allows you to backup and save your currently active .htaccess file should you need to re-use the the backed up file in the future."
msgstr "Met deze functie kunt u een back-up maken en uw momenteel actieve .htaccess-bestand opslaan als u het back-upbestand in de toekomst opnieuw moet gebruiken."

#: admin/wp-security-settings-menu.php:413
msgid "You can also restore your site's .htaccess settings using a backed up .htaccess file."
msgstr "U kunt ook de .htaccess-instellingen van uw site herstellen met behulp van een .htaccess-bestand waarvan een back-up is gemaakt."

#: admin/wp-security-settings-menu.php:428
msgid "Save the current .htaccess file"
msgstr "Sla het huidige .htaccess-bestand op"

#: admin/wp-security-settings-menu.php:432
msgid "Click the button below to backup and save the currently active .htaccess file."
msgstr "Klik op de onderstaande knop om een back-up te maken van het momenteel actieve .htaccess-bestand en het op te slaan."

#: admin/wp-security-settings-menu.php:437
msgid "Restore from a backed up .htaccess file"
msgstr "Herstellen van een back-up van .htaccess-bestand"

#: admin/wp-security-settings-menu.php:443
msgid ".htaccess file to restore from"
msgstr ".htaccess-bestand om van te herstellen"

#: admin/wp-security-settings-menu.php:445
msgid "Select Your htaccess File"
msgstr ""

#: admin/wp-security-settings-menu.php:449
msgid "After selecting your file, click the button below to restore your site using the backed up htaccess file (htaccess_backup.txt)."
msgstr "Na het selecteren van uw bestand, klikt u op de onderstaande knop om uw site te herstellen met behulp van het back-up htaccess-bestand (htaccess_backup.txt)."

#: admin/wp-security-settings-menu.php:455
msgid "Restore .htaccess file"
msgstr "Herstel .htaccess-bestand"

#: admin/wp-security-settings-menu.php:477
msgid "Please choose a wp-config.php file to restore from."
msgstr "Kies een wp-config.php bestand om te herstellen van."

#: admin/wp-security-settings-menu.php:493
msgid "wp-config.php file restore failed. Please attempt to restore this file manually using FTP."
msgstr "wp-config.php bestand herstellen mislukt. Probeer dit bestand handmatig te herstellen met behulp van FTP."

#: admin/wp-security-settings-menu.php:497
msgid "Your wp-config.php file has successfully been restored!"
msgstr "Uw wp-config.php bestand is succesvol hersteld!"

#: admin/wp-security-settings-menu.php:503
msgid "wp-config.php Restore operation failed! Please check the contents of the file you are trying to restore from."
msgstr "wp-config.php-herstelbewerking mislukt! Controleer de inhoud van het bestand dat u probeert te herstellen."

#: admin/wp-security-settings-menu.php:509
msgid "wp-config.php file operations"
msgstr "wp-config.php-bestandsbewerkingen"

#: admin/wp-security-settings-menu.php:512
msgid "Your \"wp-config.php\" file is one of the most important in your WordPress installation. It is a primary configuration file and contains crucial things such as details of your database and other critical components."
msgstr "Uw \"wp-config.php\"-bestand is een van de belangrijkste in uw WordPress-installatie. Het is een primair configuratiebestand en bevat cruciale dingen zoals details van uw database en andere kritieke componenten."

#: admin/wp-security-settings-menu.php:513
msgid "This feature allows you to backup and save your currently active wp-config.php file should you need to re-use the the backed up file in the future."
msgstr "Met deze functie kunt u een back-up maken van uw momenteel actieve wp-config.php-bestand en dit opslaan, mocht u het back-upbestand in de toekomst opnieuw moeten gebruiken."

#: admin/wp-security-settings-menu.php:514
msgid "You can also restore your site's wp-config.php settings using a backed up wp-config.php file."
msgstr "U kunt ook de wp-config.php-instellingen van uw site herstellen met behulp van een back-up van een wp-config.php-bestand."

#: admin/wp-security-settings-menu.php:529
msgid "Save the current wp-config.php file"
msgstr "Sla het huidige bestand wp-config.php op"

#: admin/wp-security-settings-menu.php:533
msgid "Click the button below to backup and download the contents of the currently active wp-config.php file."
msgstr "Klik op de onderstaande knop om de inhoud van het momenteel actieve bestand wp-config.php te back-uppen en te downloaden ."

#: admin/wp-security-settings-menu.php:539
msgid "Restore from a backed up wp-config file"
msgstr "Herstel van een geback-upt wp-config-bestand"

#: admin/wp-security-settings-menu.php:545
msgid "wp-config file to restore from"
msgstr "wp-config-bestand om van te herstellen"

#: admin/wp-security-settings-menu.php:547
msgid "Select Your wp-config File"
msgstr ""

#: admin/wp-security-settings-menu.php:551
msgid "After selecting your file click the button below to restore your site using the backed up wp-config file (wp-config.php.backup.txt)."
msgstr "Nadat u uw bestand hebt geselecteerd, klikt u op de onderstaande knop om uw site te herstellen met behulp van het back-upbestand wp-config (wp-config.php.backup.txt)."

#: admin/wp-security-settings-menu.php:557
msgid "Restore wp-config file"
msgstr "Herstel wp-config-bestand"

#: admin/wp-security-settings-menu.php:591
msgid "Manage delete plugin settings saved."
msgstr ""

#: admin/wp-security-settings-menu.php:596
msgid "Manage delete plugin tasks"
msgstr ""

#: admin/wp-security-settings-menu.php:603
msgid "Delete database tables"
msgstr ""

#: admin/wp-security-settings-menu.php:606
msgid "Check this if you want to remove database tables when the plugin is uninstalled."
msgstr ""

#: admin/wp-security-settings-menu.php:610
msgid "Delete settings"
msgstr ""

#: admin/wp-security-settings-menu.php:613
msgid "Check this if you want to remove all plugin settings when uninstalling the plugin."
msgstr ""

#: admin/wp-security-settings-menu.php:613
msgid "It will also remove all custom htaccess rules that were added by this plugin."
msgstr ""

#: admin/wp-security-settings-menu.php:647
msgid "WP generator meta tag and version info"
msgstr ""

#: admin/wp-security-settings-menu.php:650
msgid "WordPress generator automatically adds some meta information inside the \"head\" tags of every page on your site's front end. Below is an example of this:"
msgstr "De WordPress-generator voegt automatisch wat meta-informatie toe aan de voorkant van de site op de \"head\" -tags van elke pagina . Hieronder is een voorbeeld hiervan:"

#: admin/wp-security-settings-menu.php:652
msgid "The above meta information shows which version of WordPress your site is currently running and thus can help hackers or crawlers scan your site to see if you have an older version of WordPress or one with a known exploit."
msgstr "De bovenstaande meta-informatie laat zien welke versie van WordPress uw site momenteel gebruikt en kan zo helpen bij het door hackers of crawlers scannen van uw site om te zien of u een oudere versie van WordPress of een versie met een bekende exploit heeft."

#: admin/wp-security-settings-menu.php:653
msgid "There are also other ways wordpress reveals version info such as during style and script loading. An example of this is:"
msgstr "Er zijn ook andere manieren waarop Wordpress informatie over de versie onthult, zoals tijdens het laden van stijlen en scripts. Een voorbeeld hiervan is:"

#: admin/wp-security-settings-menu.php:655
msgid "This feature will allow you to remove the WP generator meta info and other version info from your site's pages."
msgstr "Deze functie zal het toelaten dat de WP-generator meta-informatie en andere versie-informatie van uw website 's pagina's verwijdt."

#: admin/wp-security-settings-menu.php:661
msgid "WP generator meta info"
msgstr "WP Generator meta-info"

#: admin/wp-security-settings-menu.php:673
msgid "Remove WP generator meta info"
msgstr "Verwijder WP Generator meta-info"

#: admin/wp-security-settings-menu.php:676
msgid "Check this if you want to remove the version and meta info produced by WP from all pages"
msgstr "Vink dit aan als u de versie en meta-info van WP van alle pagina's wilt verwijderen"

#: admin/wp-security-settings-menu.php:704
msgid "Please choose a file to import your settings from."
msgstr "Kies een bestand om uw instellingen van te importeren ."

#: admin/wp-security-settings-menu.php:736
msgid "Import AIOS settings from "
msgstr ""

#: admin/wp-security-settings-menu.php:742
#: admin/wp-security-settings-menu.php:786
msgid "The deletion of the import file failed. Please delete this file manually via the media menu for security purposes."
msgstr "Het verwijderen van het importbestand is mislukt. Gelieve dit bestand handmatig te verwijderen via het media-menu voor beveiligingsdoeleinden."

#: admin/wp-security-settings-menu.php:744
#: admin/wp-security-settings-menu.php:788
msgid "The file you uploaded was also deleted for security purposes because it contains security settings details."
msgstr "Het bestand dat u hebt geüpload, is ook om veiligheidsredenen verwijderd omdat het beveiligingsinstellingen bevat."

#: admin/wp-security-settings-menu.php:759
msgid "Your AIOS settings were successfully imported via file input."
msgstr ""

#: admin/wp-security-settings-menu.php:760
msgid "The deletion of the import file failed. Please delete this file manually via the media menu for security purposes because it contains security settings details."
msgstr "Het verwijderen van het importbestand is mislukt. Gelieve dit bestand handmatig te verwijderen via het media-menu voor beveiligingsdoeleinden, want dit bevat details van beveiligingsinstellingen."

#: admin/wp-security-settings-menu.php:762
msgid "Your AIOS settings were successfully imported. The file you uploaded was also deleted for security purposes because it contains security settings details."
msgstr ""

#: admin/wp-security-settings-menu.php:765
msgid "Your AIOS settings were successfully imported via text entry."
msgstr ""

#: admin/wp-security-settings-menu.php:780
msgid "The contents of your settings file appear invalid. Please check the contents of the file you are trying to import settings from."
msgstr "De inhoud van uw instellingenbestand lijkt ongeldig. Controleer de inhoud van het bestand waarvan u de instellingen probeert te importeren."

#: admin/wp-security-settings-menu.php:797
msgid "Export or import your AIOS settings"
msgstr ""

#: admin/wp-security-settings-menu.php:800
msgid "This section allows you to export or import your All In One WP Security & Firewall settings."
msgstr "In dit gedeelte kunt u uw All In One WP Security & Firewall-instellingen exporteren of importeren ."

#: admin/wp-security-settings-menu.php:801
msgid "This can be handy if you wanted to save time by applying the settings from one site to another site."
msgstr "Dit kan handig zijn als u tijd wilt besparen door de instellingen van de ene site naar een andere site toe te passen ."

#: admin/wp-security-settings-menu.php:802
msgid "NOTE: Before importing, it is your responsibility to know what settings you are trying to import. Importing settings blindly can cause you to be locked out of your site."
msgstr "OPMERKING: Voordat u importeert, is het uw verantwoordelijkheid om te weten welke instellingen u probeert te importeren. Het importeren van instellingen blindelings kan ertoe leiden dat u om te worden uitgesloten van uw website ."

#: admin/wp-security-settings-menu.php:803
msgid "For Example: If a settings item relies on the domain URL then it may not work correctly when imported into a site with a different domain."
msgstr "Voorbeeld: als een instellingsitem afhankelijk is van de domein-URL, werkt deze mogelijk niet correct als deze wordt geïmporteerd in een site met een ander domein."

#: admin/wp-security-settings-menu.php:809
#: admin/wp-security-settings-menu.php:818
msgid "Export AIOS settings"
msgstr ""

#: admin/wp-security-settings-menu.php:815
msgid "To export your All In One WP Security & Firewall settings click the button below."
msgstr "Klik op de onderstaande knop om uw All In One WP Security & Firewall-instellingen te exporteren ."

#: admin/wp-security-settings-menu.php:822
#: admin/wp-security-settings-menu.php:851
msgid "Import AIOS settings"
msgstr ""

#: admin/wp-security-settings-menu.php:828
msgid "Use this section to import your All In One WP Security & Firewall settings from a file. Alternatively, copy/paste the contents of your import file into the textarea below."
msgstr "Gebruik dit gedeelte om uw All In One WP Security & Firewall-instellingen uit een bestand te importeren . Of kopieer en plak de inhoud van uw importbestand in het onderstaande tekstgebied."

#: admin/wp-security-settings-menu.php:830
msgid "Import file"
msgstr "Importeer bestand"

#: admin/wp-security-settings-menu.php:833
msgid "Select Your Import Settings File"
msgstr ""

#: admin/wp-security-settings-menu.php:837
msgid "After selecting your file, click the button below to apply the settings to your site."
msgstr "Nadat u uw bestand hebt geselecteerd, klikt u op de onderstaande knop om de instellingen op uw site toe te passen ."

#: admin/wp-security-settings-menu.php:844
msgid "Copy/Paste import data"
msgstr "Importeer gegevens en plak ze"

#: admin/wp-security-settings-menu.php:893
msgid "Default - if correct, then this is the best option"
msgstr ""

#: admin/wp-security-settings-menu.php:894
msgid "Only use if you're using Cloudflare."
msgstr ""

#: admin/wp-security-settings-menu.php:902
msgid "(current value: %s)"
msgstr ""

#: admin/wp-security-settings-menu.php:905
msgid "no value (i.e. empty) on your server"
msgstr ""

#: admin/wp-security-spam-menu.php:28
msgid "Comment spam"
msgstr "Reactie SPAM"

#: admin/wp-security-spam-menu.php:29
msgid "Comment spam IP monitoring"
msgstr "Bewaking commentaar SPAM IP"

#: admin/wp-security-spam-menu.php:30
msgid "BuddyPress"
msgstr "BuddyPress"

#: admin/wp-security-spam-menu.php:31
msgid "bbPress"
msgstr "BBPress"

#: admin/wp-security-spam-menu.php:57
msgid "Spam prevention"
msgstr "SPAM voorkomen"

#: admin/wp-security-spam-menu.php:99
msgid "You entered a non numeric value for the \"move spam comments to trash after number of days\" field."
msgstr ""

#: admin/wp-security-spam-menu.php:99
#: admin/wp-security-spam-menu.php:297
#: admin/wp-security-user-login-menu.php:118
#: admin/wp-security-user-login-menu.php:124
#: admin/wp-security-user-login-menu.php:130
#: admin/wp-security-user-login-menu.php:136
msgid "It has been set to the default value."
msgstr ""

#: admin/wp-security-spam-menu.php:129
msgid "Comment spam settings"
msgstr "Commentaar SPAM-instellingen"

#: admin/wp-security-spam-menu.php:134
msgid "Add CAPTCHA to comments form"
msgstr "Voeg Captcha toe aan commentaarformulieren"

#: admin/wp-security-spam-menu.php:138
msgid "This feature will add a CAPTCHA field in the WordPress comments form."
msgstr ""

#: admin/wp-security-spam-menu.php:139
msgid "Adding a CAPTCHA field in the comment form is a simple way of greatly reducing spam comments from bots without using .htaccess rules."
msgstr "Het toevoegen van een captcha-veld in het reactieformulier is een eenvoudige manier om SPAM-opmerkingen van bots te verminderen zonder de .htaccess-regels te gebruiken."

#: admin/wp-security-spam-menu.php:148
msgid "Enable CAPTCHA on comment forms"
msgstr "Schakel Captcha op opmerkingenformulier in"

#: admin/wp-security-spam-menu.php:151
msgid "Check this if you want to insert a CAPTCHA field on the comment forms."
msgstr "Selecteer dit als u een captcha-veld wil invoegen op de commentaarformulieren"

#: admin/wp-security-spam-menu.php:158
msgid "Block spambot comments"
msgstr "Spambot-opmerkingen blokkeren"

#: admin/wp-security-spam-menu.php:162
msgid "A large portion of WordPress blog comment spam is mainly produced by automated bots and not necessarily by humans."
msgstr ""

#: admin/wp-security-spam-menu.php:163
msgid "This feature will greatly minimize the useless and unecessary traffic and load on your server resulting from spam comments by blocking all comment requests which do not originate from your domain."
msgstr "Deze functie zal sterk het nutteloze en onnodige verkeer en de belasting van uw server, als gevolg van SPAM-reacties, minimaliseren, door het blokkeren van alle commentaarverzoeken die niet afkomstig zijn van uw domein."

#: admin/wp-security-spam-menu.php:164
msgid "In other words, if the comment was not submitted by a human who physically submitted the comment on your site, the request will be blocked."
msgstr "Met andere woorden, als de reactie niet werd ingediend door een mens die fysiek de reactie op uw website plaatste, zal het verzoek worden geblokkeerd ."

#: admin/wp-security-spam-menu.php:182
msgid "Block spambots from posting comments"
msgstr "Block spambots voor het plaatsen van commentaren"

#: admin/wp-security-spam-menu.php:185
msgid "Check this if you want to apply a firewall rule which will block comments originating from spambots."
msgstr "Selecteer dit als u een firewall-regel wilt toepassen die opmerkingen afkomstig van spambots blokkeert."

#: admin/wp-security-spam-menu.php:189
msgid "This feature will implement a firewall rule to block all comment attempts which do not originate from your domain."
msgstr "Met deze functie wordt een firewall-regel geïmplementeerd om alle opmerkingen te blokkeren die niet afkomstig zijn uit uw domein."

#: admin/wp-security-spam-menu.php:190
msgid "A legitimate comment is one which is submitted by a human who physically fills out the comment form and clicks the submit button. For such events, the HTTP_REFERRER is always set to your own domain."
msgstr "Een legitieme opmerking is een opmerking die wordt ingediend door een persoon die het opmerkingenformulier fysiek invult en op de knop Verzenden klikt. Voor dergelijke gebeurtenissen is de HTTP_REFERRER altijd ingesteld op uw eigen domein."

#: admin/wp-security-spam-menu.php:191
msgid "A comment submitted by a spambot is done by directly calling the comments.php file, which usually means that the HTTP_REFERRER value is not your domain and often times empty."
msgstr "Een opmerking die door een spambot wordt ingediend, wordt gedaan door rechtstreeks het bestand comments.php op te roepen. Dit betekent meestal dat de waarde HTTP_REFERRER niet uw domein is en vaak leeg."

#: admin/wp-security-spam-menu.php:192
msgid "This feature will check and block comment requests which are not referred by your domain thus greatly reducing your overall blog spam and PHP requests done by the server to process these comments."
msgstr "Deze functie zal commentaarverzoeken controleren en blokkeren die niet afkomstig zijn van uw domein en zo uw totale blog-SPAM en PHP-verzoeken, gedaan door de server om deze te verwerken, sterk verminderen."

#: admin/wp-security-spam-menu.php:202
msgid "Comment processing"
msgstr ""

#: admin/wp-security-spam-menu.php:207
msgid "Trash spam comments"
msgstr ""

#: admin/wp-security-spam-menu.php:216
msgid "Move spam comments to trash after %s days."
msgstr ""

#: admin/wp-security-spam-menu.php:224
msgid "Enble this feature in order to move the spam comments to trash after given number of days."
msgstr ""

#: admin/wp-security-spam-menu.php:262
msgid "You entered a non numeric value for the minimum number of spam comments field. It has been set to the default value."
msgstr "U hebt een niet numerieke waarde ingevoerd voor het minimumaantal spam-opmerkingen . Het is ingesteld op de standaardwaarde."

#: admin/wp-security-spam-menu.php:265
msgid "You must enter an integer greater than zero for minimum number of spam comments field. It has been set to the default value."
msgstr "Je moet een geheel getal groter dan nul invullen voor het minimum aantal spam-opmerkingenveld. Het is ingesteld op de standaardwaarde."

#: admin/wp-security-spam-menu.php:292
msgid "Nonce check failed for list spam comment IPs."
msgstr "Nonce check mislukt voor lijst SPAM-comment IP's!"

#: admin/wp-security-spam-menu.php:297
msgid "You entered a non numeric value for the minimum spam comments per IP field."
msgstr ""

#: admin/wp-security-spam-menu.php:308
msgid "Displaying results for IP addresses which have posted a minimum of %s spam comments."
msgstr "Resultaten weergeven voor IP-adressen die minimaal %s SPAM-opmerkingen hebben gepost"

#: admin/wp-security-spam-menu.php:323
msgid "Auto block spammer IPs"
msgstr "Blokkeer SPAMMER IP's automatisch"

#: admin/wp-security-spam-menu.php:328
msgid "This feature has detected that %s is not active. It is highly recommended that you activate the Akismet plugin to make the most of this feature."
msgstr "Deze functie heeft dat gedetecteerd dat %s niet actief is. Het wordt ten zeerste aanbevolen dat u de Akismet-plug- in activeert om het beste uit deze functie te halen."

#: admin/wp-security-spam-menu.php:337
msgid "This feature allows you to automatically and permanently block IP addresses which have exceeded a certain number of comments labelled as spam."
msgstr "Met deze functie kunt u automatisch en permanent IP-adressen blokkeren die een bepaald aantal opmerkingen met het label SPAM hebben overschreden ."

#: admin/wp-security-spam-menu.php:338
msgid "Comments are usually labelled as spam either by the Akismet plugin or manually by the WP administrator when they mark a comment as \"spam\" from the WordPress Comments menu."
msgstr "Opmerkingen worden meestal als SPAM aangeduid door de Akismet-plug-in of handmatig door de WP-beheerder wanneer ze een opmerking markeren als \"spam\" in het menu WordPress Comments  ."

#: admin/wp-security-spam-menu.php:352
msgid "You currently have no IP addresses permanently blocked due to spam."
msgstr "Je hebt momenteel geen IP-adressen geblokkeerd vanwege SPAM."

#: admin/wp-security-spam-menu.php:365
msgid "Spammer IPs added to permanent block list today: "
msgstr "Spammer IP's vandaag toegevoegd aan de blokkadelijst: "

#: admin/wp-security-spam-menu.php:366
msgid "All time total: "
msgstr "Totaal: "

#: admin/wp-security-spam-menu.php:367
msgid "View blocked IPs"
msgstr "Bekijk geblokkeerde IP's"

#: admin/wp-security-spam-menu.php:380
msgid "Enable auto block of spam comment IPs"
msgstr "Maak gebruik van automatisch blokkeren van SPAM-reacties IP's"

#: admin/wp-security-spam-menu.php:383
msgid "Check this box if you want this plugin to automatically block IP addresses which submit spam comments."
msgstr "Schakel dit selectievakje in als u wilt dat deze plug- in automatisch IP-adressen blokkeert die SPAM-opmerkingen indienen ."

#: admin/wp-security-spam-menu.php:387
msgid "Minimum number of spam comments"
msgstr "Minimaal aantal SPAM-reacties"

#: admin/wp-security-spam-menu.php:389
msgid "Specify the minimum number of spam comments for an IP address before it is permanently blocked."
msgstr "Vul het minimum aantal SPAM-reacties per IP-adres in voordat het permanent geblokkeerd wordt."

#: admin/wp-security-spam-menu.php:393
msgid "Example 1: Setting this value to \"1\" will block ALL IP addresses which were used to submit at least one spam comment."
msgstr "Voorbeeld 1: Wanneer je \"1\" invult als waarde zal het alle IP-adressen blokkeren die minimaal 1 SPAM-reactie hebben geplaatst op jouw website."

#: admin/wp-security-spam-menu.php:394
msgid "Example 2: Setting this value to \"5\" will block only those IP addresses which were used to submit 5 spam comments or more on your site."
msgstr "Voorbeeld 2: Wanneer je \"5\" invult als waarde zal het alle IP-adressen blokkeren die 5 of meer SPAM-reacties hebben geplaatst op jouw website."

#: admin/wp-security-spam-menu.php:412
msgid "List spammer IP addresses"
msgstr "Lijst SPAMMER IP-adressen"

#: admin/wp-security-spam-menu.php:416
msgid "This section displays a list of the IP addresses of the people or bots who have left spam comments on your site."
msgstr "In deze sectie wordt een lijst weergegeven met de IP-adressen van de mensen of bots die SPAM-opmerkingen op uw site hebben achtergelaten ."

#: admin/wp-security-spam-menu.php:417
msgid "This information can be handy for identifying the most persistent IP addresses or ranges used by spammers."
msgstr "Deze informatie kan handig zijn voor het identificeren van de meest persistente IP-adressen of bereiken die worden gebruikt door spammers."

#: admin/wp-security-spam-menu.php:418
msgid "By inspecting the IP address data coming from spammers you will be in a better position to determine which addresses or address ranges you should block by adding them to the permanent block list."
msgstr "Door de IP-adresgegevens te controleren die afkomstig zijn van spammers, bent u beter in staat om te bepalen welke adressen of adresbereiken u moet blokkeren door ze toe te voegen aan de permanente blokkeerlijst ."

#: admin/wp-security-spam-menu.php:419
msgid "To add one or more of the IP addresses displayed in the table below to your blacklist, simply click the \"Block\" link for the individual row or select more than one address using the checkboxes and then choose the \"block\" option from the Bulk Actions dropdown list and click the \"Apply\" button."
msgstr ""

#: admin/wp-security-spam-menu.php:427
msgid "Minimum number of spam comments per IP"
msgstr "Minimaal aantal SPAM-opmerkingen per IP"

#: admin/wp-security-spam-menu.php:429
msgid "This field allows you to list only those IP addresses which have been used to post X or more spam comments."
msgstr "In dit veld kunt u alleen de IP-adressen tonen die zijn gebruikt om X of meer SPAM-reacties te posten."

#: admin/wp-security-spam-menu.php:433
msgid "Example 1: Setting this value to \"0\" or \"1\" will list ALL IP addresses which were used to submit spam comments."
msgstr "Voorbeeld 1: door deze waarde in te stellen op \"0\" of \"1\" worden ALLE IP-adressen vermeld die zijn gebruikt om SPAM-opmerkingen in te dienen ."

#: admin/wp-security-spam-menu.php:434
msgid "Example 2: Setting this value to \"5\" will list only those IP addresses which were used to submit 5 spam comments or more on your site."
msgstr "Voorbeeld 2: als u deze waarde instelt op \"5\", worden alleen die IP-adressen vermeld die zijn gebruikt om 5 SPAM-opmerkingen of meer op uw site in te dienen ."

#: admin/wp-security-spam-menu.php:441
msgid "Find IP addresses"
msgstr "Zoek IP-adressen"

#: admin/wp-security-spam-menu.php:445
msgid "Spammer IP address results"
msgstr "SPAMMER IP-adres resultaten"

#: admin/wp-security-spam-menu.php:451
#: classes/wp-security-utility.php:253
msgid "The plugin has detected that you are using a Multi-Site WordPress installation."
msgstr "De plug-in heeft gedetecteerd dat u een multi-site WordPress-installatie gebruikt."

#: admin/wp-security-spam-menu.php:452
msgid "Only the \"superadmin\" can block IP addresses from the main site."
msgstr "Alleen de \"superadmin\" kan IP-adressen van de hoofdsite blokkeren."

#: admin/wp-security-spam-menu.php:453
msgid "Take note of the IP addresses you want blocked and ask the superadmin to add these to the blacklist using the \"Blacklist Manager\" on the main site."
msgstr "Neem kennis van de IP-adressen die u wilt blokkeren en vraag de superadmin om deze toe te voegen aan de zwarte lijst met behulp van de \"zwarte lijst Manager\" op de hoofdwebsite."

#: admin/wp-security-spam-menu.php:498
msgid "BuddyPress spam settings"
msgstr "BuddyPress SPAM-instellingen"

#: admin/wp-security-spam-menu.php:503
msgid "Add CAPTCHA to BuddyPress registration form"
msgstr "Voeg Captcha toe aan het BuddyPress-registratieformulier"

#: admin/wp-security-spam-menu.php:507
msgid "This feature will add a simple math CAPTCHA field in the BuddyPress registration form."
msgstr "Met deze functie toe te voegen een eenvoudig wiskunde-captcha-veld in het BuddyPress-inschrijfformulier."

#: admin/wp-security-spam-menu.php:508
msgid "Adding a CAPTCHA field in the registration form is a simple way of greatly reducing spam signups from bots without using .htaccess rules."
msgstr "Het toevoegen van een captcha-veld in het registratieformulier is een eenvoudige manier om SPAM-registraties van bots te verminderen zonder de .htaccess-regels te gebruiken."

#: admin/wp-security-spam-menu.php:518
msgid "Enable CAPTCHA on BuddyPress registration form"
msgstr "Gebruik captcha voor BuddyPress registratieformulier"

#: admin/wp-security-spam-menu.php:521
msgid "Check this if you want to insert a CAPTCHA field on the BuddyPress registration forms."
msgstr "Vink dit aan als je een captcha-veld wilt toevoegen aan het BuddyPress-registratieformulier"

#: admin/wp-security-spam-menu.php:530
msgid "BuddyPress is not active! In order to use this feature you will need to have BuddyPress installed and activated."
msgstr "BuddyPress is niet actief! Om deze optie gebruiken moet BuddyPress geïnstalleerd en geactiveerd zijn."

#: admin/wp-security-spam-menu.php:560
msgid "bbPress spam settings"
msgstr "BBPress SPAM-instellingen"

#: admin/wp-security-spam-menu.php:565
msgid "Add CAPTCHA to bbPress new topic form"
msgstr "Voeg Captcha toe aan het BBPress nieuw onderwerp formulier"

#: admin/wp-security-spam-menu.php:569
msgid "This feature will add a simple math CAPTCHA field in the bbPress new topic form."
msgstr "Deze functie voegt een eenvoudige math CAPTCHA veld toe aan het BBPress nieuw topic formulier."

#: admin/wp-security-spam-menu.php:570
msgid "Adding a CAPTCHA field in this form is a simple way of greatly reducing spam submitted from bots."
msgstr ""

#: admin/wp-security-spam-menu.php:580
msgid "Enable CAPTCHA on bbPress new topic form"
msgstr "Gebruik Captcha op het BBPress Nieuw Onderwerp Formulier"

#: admin/wp-security-spam-menu.php:583
msgid "Check this if you want to insert a CAPTCHA field on the bbPress new topic forms."
msgstr "Vink dit aan als u een captcha-veld wilt invoegen op de BBPress nieuwe onderwerpformulieren"

#: admin/wp-security-spam-menu.php:592
msgid "bbPress is not active. In order to use this feature you will need to have bbPress installed and activated."
msgstr ""

#: admin/wp-security-tools-menu.php:34
msgid "WHOIS lookup"
msgstr "WHOIS Lookup"

#: admin/wp-security-tools-menu.php:95
#: admin/wp-security-tools-menu.php:136
msgid "Querying %s: %s"
msgstr ""

#: admin/wp-security-tools-menu.php:103
#: admin/wp-security-tools-menu.php:112
#: admin/wp-security-tools-menu.php:151
msgid "Redirected to %s"
msgstr ""

#: admin/wp-security-tools-menu.php:173
msgid "The WHOIS lookup feature gives you a way to look up who owns an IP address or domain name."
msgstr ""

#: admin/wp-security-tools-menu.php:173
msgid "You can use this to investigate users engaging in malicious activity on your site."
msgstr ""

#: admin/wp-security-tools-menu.php:176
msgid "WHOIS lookup on IP or domain"
msgstr ""

#: admin/wp-security-tools-menu.php:183
msgid "IP address or domain name:"
msgstr ""

#: admin/wp-security-tools-menu.php:190
msgid "Look up IP or domain"
msgstr ""

#: admin/wp-security-tools-menu.php:219
msgid "Please enter a valid IP address or domain name to look up."
msgstr ""

#: admin/wp-security-tools-menu.php:220
#: admin/wp-security-tools-menu.php:226
msgid "Nothing to show."
msgstr ""

#: admin/wp-security-user-accounts-menu.php:32
msgid "WP username"
msgstr "WP-gebruikersnaam"

#: admin/wp-security-user-accounts-menu.php:33
msgid "Display name"
msgstr "Schermnaam"

#: admin/wp-security-user-accounts-menu.php:34
msgid "Password"
msgstr "Wachtwoord"

#: admin/wp-security-user-accounts-menu.php:60
msgid "User accounts"
msgstr "Gebruikersaccounts"

#: admin/wp-security-user-accounts-menu.php:82
msgid "Admin user security"
msgstr "Administrator-beveiliging"

#: admin/wp-security-user-accounts-menu.php:85
msgid "By default, WordPress sets the administrator username to \"admin\" at installation time."
msgstr "Standaard gebruikt WordPress \"admin\" als gebruikersnaam."

#: admin/wp-security-user-accounts-menu.php:86
msgid "A lot of hackers try to take advantage of this information by attempting \"Brute force login attacks\" where they repeatedly try to guess the password by using \"admin\" for username."
msgstr "Veel hackers maken hier gebruik van met \"Brute Force loginaanvallen\" waarbij continu wordt geprobeerd in te loggen met de gebruikersnaam \"admin\"."

#: admin/wp-security-user-accounts-menu.php:87
msgid "From a security perspective, changing the default \"admin\" user name is one of the first and smartest things you should do on your site."
msgstr "Voor beveiliging is het veranderen van de \"admin\"-gebruikersnaam een van de eerste en slimste dingen om te doen."

#: admin/wp-security-user-accounts-menu.php:88
msgid "This feature will allow you to change your default \"admin\" user name to a more secure name of your choosing."
msgstr "Hiermee kan je de standaard \"admin\"-gebruikersnaam wijzigen naar een veiligere naam."

#: admin/wp-security-user-accounts-menu.php:95
msgid "List of administrator accounts"
msgstr "Lijst van administrator-accounts"

#: admin/wp-security-user-accounts-menu.php:104
#: classes/grade-system/wp-security-feature-item-manager.php:43
msgid "Change admin username"
msgstr "Verander admin-gebruikersnaam"

#: admin/wp-security-user-accounts-menu.php:112
msgid "Your site currently has an account which uses the default \"admin\" username. It is highly recommended that you change this name to something else. Use the following field to change the admin username."
msgstr "Je site heeft momenteel een gebruiker die de standaard \"admin\"-gebruikersnaam heeft. Het wordt aangeraden om die te veranderen in iets anders. Gebruik het volgende veld om de gebruikersnaam te wijzigen."

#: admin/wp-security-user-accounts-menu.php:118
msgid "New admin username"
msgstr "Nieuwe admin-gebruikersnaam"

#: admin/wp-security-user-accounts-menu.php:120
msgid "Choose a new username for admin."
msgstr "Kies een nieuwe gebruikersnaam voor admin."

#: admin/wp-security-user-accounts-menu.php:124
msgid "Change username"
msgstr "Verander gebruikersnaam"

#: admin/wp-security-user-accounts-menu.php:126
msgid "NOTE: If you are currently logged in as \"admin\" you will be automatically logged out after changing your username and will be required to log back in."
msgstr "LET OP: Als je momenteel ingelogd bent als \"admin\" zal je uitgelogd worden na het wijzigen van je gebruikersnaam en opnieuw moeten inloggen."

#: admin/wp-security-user-accounts-menu.php:133
msgid "No action required! "
msgstr "Geen actie nodig! "

#: admin/wp-security-user-accounts-menu.php:135
msgid "Your site does not have any account which uses the default \"admin\" username. "
msgstr "Jouw site heeft geen gebruiker met de standaard \"admin\"-gebruikersnaam. "

#: admin/wp-security-user-accounts-menu.php:136
msgid "This is good security practice."
msgstr "Dit is goede beveiliging."

#: admin/wp-security-user-accounts-menu.php:148
msgid "Display name security"
msgstr "Weergavenaam beveiliging"

#: admin/wp-security-user-accounts-menu.php:151
msgid "When you submit a post or answer a comment, WordPress will usually display your \"nickname\"."
msgstr "Als je een bericht of reactie plaatst zal WordPress automatisch jouw gebruikersnaam weergeven."

#: admin/wp-security-user-accounts-menu.php:152
msgid "By default the nickname is set to the login (or user) name of your account."
msgstr "Standaard is de schermnaam hetzelfde als de gebruikersnaam van je account."

#: admin/wp-security-user-accounts-menu.php:153
msgid "From a security perspective, leaving your nickname the same as your user name is bad practice because it gives a hacker at least half of your account's login credentials."
msgstr "Voor beveiliging is het slecht om je schermnaam hetzelfde te laten als je gebruikersnaam omdat het een hacker de helft van je inloggegevens geeft."

#: admin/wp-security-user-accounts-menu.php:154
msgid "Therefore to further tighten your site's security you are advised to change your <strong>nickname</strong> and <strong>Display name</strong> to be different from your <strong>Username</strong>."
msgstr "Daarom is het aangeraden om je <strong>schermnaam</strong> en <strong>schermnaam (zoals getoond op de site)</strong> anders te maken dan je <strong>gebruikersnaam</strong>."

#: admin/wp-security-user-accounts-menu.php:160
msgid "Modify accounts with identical login name and display name"
msgstr ""

#: admin/wp-security-user-accounts-menu.php:169
msgid "Your site currently has the following accounts which have an identical login name and display name."
msgstr "Bij de volgende gebruikers op jouw site zijn de schermnaam en de gebruikersnaam hetzelfde."

#: admin/wp-security-user-accounts-menu.php:170
msgid "Follow the link to edit the user profile of that particular user account, change Nickname, choose a different Display name compared to Username, and press the \"Update User\" button.)"
msgstr ""

#: admin/wp-security-user-accounts-menu.php:185
msgid "No action required."
msgstr "Geen actie nodig."

#: admin/wp-security-user-accounts-menu.php:186
msgid "Your site does not have a user account where the display name is identical to the username."
msgstr "Jouw site heeft geen gebruikers waar het schermnaam identiek is aan de gebruikersnaam."

#: admin/wp-security-user-accounts-menu.php:197
msgid "Password tool"
msgstr "Wachtwoord-tool"

#: admin/wp-security-user-accounts-menu.php:200
msgid "Poor password selection is one of the most common weak points of many sites and is usually the first thing a hacker will try to exploit when attempting to break into your site."
msgstr "Slechte wachtwoordselectie is een van de meest voorkomende zwakke punten van veel sites en is meestal het eerste wat een hacker probeert te misbruiken wanneer hij probeert in te breken op uw site ."

#: admin/wp-security-user-accounts-menu.php:201
msgid "Many people fall into the trap of using a simple word or series of numbers as their password. Such a predictable and simple password would take a competent hacker merely minutes to guess your password by using a simple script which cycles through the easy and most common combinations."
msgstr "Veel mensen raken in de val van het gebruik van een simpel woord of een reeks cijfers als wachtwoord . Een dergelijk voorspelbaar en eenvoudig wachtwoord zou een bekwame hacker slechts enkele minuten kosten om uw wachtwoord te raden met behulp van een eenvoudig script dat door de eenvoudige en meest gebruikelijke combinaties loopt."

#: admin/wp-security-user-accounts-menu.php:202
msgid "The longer and more complex your password is the harder it is for hackers to \"crack\" because more complex passwords require much greater computing power and time."
msgstr "Hoe langer en complexer uw wachtwoord is, hoe moeilijker het voor hackers is om te \"kraken\", omdat meer complexe wachtwoorden veel meer rekenkracht en tijd vereisen."

#: admin/wp-security-user-accounts-menu.php:203
msgid "This section contains a useful password strength tool which you can use to check whether your password is sufficiently strong enough."
msgstr "Dit gedeelte bevat een handig wachtwoordsterkte-tool dat u kunt gebruiken om te controleren of uw wachtwoord sterk genoeg is."

#: admin/wp-security-user-accounts-menu.php:208
msgid "Password strength tool"
msgstr "Wachtwoordsterkte-tool"

#: admin/wp-security-user-accounts-menu.php:210
msgid "This password tool uses an algorithm which calculates how long it would take for your password to be cracked using the computing power of an off-the-shelf current model desktop PC with high end processor, graphics card and appropriate password cracking software."
msgstr ""

#: admin/wp-security-user-accounts-menu.php:213
msgid "Start typing a password."
msgstr "Type een wachtwoord."

#: admin/wp-security-user-accounts-menu.php:216
msgid "It would take a desktop PC approximately"
msgstr "Het zou ongeveer een desktop-pc kosten"

#: admin/wp-security-user-accounts-menu.php:217
msgid "1 sec"
msgstr "1 seconde"

#: admin/wp-security-user-accounts-menu.php:217
msgid "to crack your password!"
msgstr "om je wachtwoord te raden!"

#: admin/wp-security-user-accounts-menu.php:222
msgid "Password Strength"
msgstr "Wachtwoordsterkte"

#: admin/wp-security-user-accounts-menu.php:245
msgid "Username "
msgstr "Gebruikersnaam "

#: admin/wp-security-user-accounts-menu.php:245
msgid " already exists. Please enter another value. "
msgstr " bestaat al. Vul iets anders in. "

#: admin/wp-security-user-accounts-menu.php:262
msgid "The database update operation of the user account failed!"
msgstr "De database-update van het gebruikersaccount is mislukt!"

#: admin/wp-security-user-accounts-menu.php:291
msgid "You entered an invalid username. Please enter another value. "
msgstr "U hebt een ongeldige gebruikersnaam ingevoerd. Voer een andere waarde in. "

#: admin/wp-security-user-accounts-menu.php:295
msgid "Please enter a value for your username. "
msgstr "Voer aub een een waarde in voor je gebruikersnaam "

#: admin/wp-security-user-accounts-menu.php:302
msgid "Username successfully changed."
msgstr "Gebruikersnaam veranderd!"

#: admin/wp-security-user-accounts-menu.php:322
msgid "Account login name"
msgstr "Account loginnaam"

#: admin/wp-security-user-accounts-menu.php:331
msgid "Edit user"
msgstr ""

#: admin/wp-security-user-login-menu.php:54
#: admin/wp-security-user-login-menu.php:474
msgid "Failed login records"
msgstr "Geschiedenis mislukte logins"

#: admin/wp-security-user-login-menu.php:55
#: classes/grade-system/wp-security-feature-item-manager.php:51
msgid "Force logout"
msgstr "Uitloggen forceren"

#: admin/wp-security-user-login-menu.php:56
#: admin/wp-security-user-login-menu.php:632
msgid "Account activity logs"
msgstr "Accountactiviteitenlogboek"

#: admin/wp-security-user-login-menu.php:58
#: admin/wp-security-user-login-menu.php:769
msgid "Additional settings"
msgstr ""

#: admin/wp-security-user-login-menu.php:81
msgid "User login"
msgstr "Gebruikerslogin"

#: admin/wp-security-user-login-menu.php:118
msgid "You entered a non-numeric value for the max login attempts field."
msgstr ""

#: admin/wp-security-user-login-menu.php:124
msgid "You entered a non numeric value for the login retry time period field."
msgstr ""

#: admin/wp-security-user-login-menu.php:130
msgid "You entered a non numeric value for the lockout time length field."
msgstr ""

#: admin/wp-security-user-login-menu.php:136
msgid "You entered a non numeric value for the maximim lockout time length field."
msgstr ""

#: admin/wp-security-user-login-menu.php:141
msgid "You entered an invalid minimum lockout time length, it must be less than the maximum lockout time length value."
msgstr ""

#: admin/wp-security-user-login-menu.php:141
msgid "Both have been set to the default values."
msgstr ""

#: admin/wp-security-user-login-menu.php:160
msgid "Please fill in one or more email addresses to notify."
msgstr ""

#: admin/wp-security-user-login-menu.php:162
msgid "You have entered one or more invalid email addresses."
msgstr ""

#: admin/wp-security-user-login-menu.php:165
msgid "It has been set to your WordPress admin email as default."
msgstr ""

#: admin/wp-security-user-login-menu.php:250
msgid "Login lockout configuration"
msgstr ""

#: admin/wp-security-user-login-menu.php:254
msgid "One of the ways hackers try to compromise sites is via a "
msgstr "Een van de manieren waarop hackers proberen sites te compromitteren is via een "

#: admin/wp-security-user-login-menu.php:254
msgid "Brute force login attack"
msgstr "Brute Force loginaanval"

#: admin/wp-security-user-login-menu.php:254
msgid "This is where attackers use repeated login attempts until they guess the password."
msgstr "Dit is waar aanvallers herhaalde inlogpogingen gebruiken totdat ze het wachtwoord raden ."

#: admin/wp-security-user-login-menu.php:255
msgid "Apart from choosing strong passwords, monitoring and blocking IP addresses which are involved in repeated login failures in a short period of time is a very effective way to stop these types of attacks."
msgstr "Afgezien van het kiezen van sterke wachtwoorden is het controleren en blokkeren van IP-adressen die in korte tijd betrokken zijn bij herhaalde inlogproblemen, een zeer effectieve manier om dit soort aanvallen te stoppen."

#: admin/wp-security-user-login-menu.php:256
msgid "You may also want to checkout our %s feature for another secure way to protect against these types of attacks."
msgstr "Misschien wilt u ook onze %s functie bekijken voor een andere veilige manier om je te beschermen tegen dit soort aanvallen."

#: admin/wp-security-user-login-menu.php:261
msgid "Login lockout options"
msgstr ""

#: admin/wp-security-user-login-menu.php:272
msgid "Enable login lockout feature"
msgstr ""

#: admin/wp-security-user-login-menu.php:275
msgid "Check this if you want to enable the login lockout feature and apply the settings below"
msgstr ""

#: admin/wp-security-user-login-menu.php:279
msgid "Allow unlock requests"
msgstr "Deblokkade-aanvraag toestaan"

#: admin/wp-security-user-login-menu.php:282
msgid "Check this if you want to allow users to generate an automated unlock request link which will unlock their account"
msgstr "Selecteer dit als u wilt toestaan dat gebruikers een verzoek kunnen genereren voor een link voor een geautomatiseerde unlock van hun account"

#: admin/wp-security-user-login-menu.php:286
msgid "Max login attempts"
msgstr "Max. loginpogingen"

#: admin/wp-security-user-login-menu.php:288
msgid "Set the value for the maximum login retries before IP address is locked out"
msgstr "Stel de waarde in voor het maximale aantal pogingen om opnieuw in te loggen voordat het IP-adres is geblokkeerd"

#: admin/wp-security-user-login-menu.php:292
msgid "Login retry time period (min)"
msgstr "Loginpogingperiode (min)"

#: admin/wp-security-user-login-menu.php:294
msgid "If the maximum number of failed login attempts for a particular IP address occur within this time period the plugin will lock out that address"
msgstr "Als het maximum aantal mislukte pogingen voor een IP-adres binnen zoveel tijd wordt overschreden zal de plug-in automatisch het adres blokkeren"

#: admin/wp-security-user-login-menu.php:299
msgid "Minimum lockout time length"
msgstr ""

#: admin/wp-security-user-login-menu.php:305
msgid "Set the minimum time period in minutes of lockout."
msgstr ""

#: admin/wp-security-user-login-menu.php:306
msgid "This failed login lockout time will be tripled on each failed login."
msgstr ""

#: admin/wp-security-user-login-menu.php:313
msgid "Maximum lockout time length"
msgstr ""

#: admin/wp-security-user-login-menu.php:318
msgid "Set the maximum time period in minutes of lockout."
msgstr ""

#: admin/wp-security-user-login-menu.php:319
msgid "No IP address will be blocked for more than this time period after making a failed login attempt."
msgstr ""

#: admin/wp-security-user-login-menu.php:324
msgid "Display generic error message"
msgstr "Aangepast foutbericht weergeven"

#: admin/wp-security-user-login-menu.php:327
msgid "Check this if you want to show a generic error message when a login attempt fails"
msgstr "Selecteer dit als u een generiek foutbericht wilt weergeven wanneer een inlogpoging mislukt"

#: admin/wp-security-user-login-menu.php:331
msgid "Instantly lockout invalid usernames"
msgstr "Direct blokkeren ongeldige gebruikersnamen"

#: admin/wp-security-user-login-menu.php:334
msgid "Check this if you want to instantly lockout login attempts with usernames which do not exist on your system"
msgstr "Vink dit aan als u inlogpogingen onmiddellijk wilt blokkeren met gebruikersnamen die niet bestaan op uw systeem"

#: admin/wp-security-user-login-menu.php:339
msgid "Instantly lockout specific usernames"
msgstr "Direct blokkeren bepaalde gebruikersnamen"

#: admin/wp-security-user-login-menu.php:349
msgid "Insert one username per line. Existing usernames are not blocked even if present in the list."
msgstr "Vul een gebruikersnaam per regel in. Bestaande gebruikersnamen worden niet geblokkeerd zelfs als deze in de lijst staan."

#: admin/wp-security-user-login-menu.php:354
msgid "Notify by email"
msgstr "Meld per e-mail"

#: admin/wp-security-user-login-menu.php:358
msgid "Check this if you want to receive an email when someone has been locked out due to maximum failed login attempts"
msgstr "Vink dit aan als u een e-mail wilt ontvangen wanneer iemand is buitengesloten vanwege een maximaal aantal mislukte inlogpogingen"

#: admin/wp-security-user-login-menu.php:361
msgid "Fill in one email address per line."
msgstr ""

#: admin/wp-security-user-login-menu.php:365
msgid "Each email address must be on a new line."
msgstr ""

#: admin/wp-security-user-login-menu.php:366
msgid "If a valid email address has not been filled in, it will not be saved."
msgstr ""

#: admin/wp-security-user-login-menu.php:367
msgid "The valid email address format is userid@example.com"
msgstr ""

#: admin/wp-security-user-login-menu.php:368
msgid "Example: %s"
msgstr ""

#: admin/wp-security-user-login-menu.php:375
msgid "Enable PHP backtrace in email"
msgstr ""

#: admin/wp-security-user-login-menu.php:379
msgid "Check this if you want to include the PHP backtrace in notification emails."
msgstr ""

#: admin/wp-security-user-login-menu.php:379
msgid "This is internal coding information which makes it easier to investigate where an issued occurred."
msgstr ""

#: admin/wp-security-user-login-menu.php:389
msgid "Currently locked out IP address ranges"
msgstr "Momenteel geblokkeerde IP-adressen"

#: admin/wp-security-user-login-menu.php:394
msgid "To see a list of all locked IP addresses and ranges go to the %s tab in the dashboard menu."
msgstr "Om een lijst van alle vergrendelde IP-adressen en bereiken te zien, gaat u naar %s tab in het dashboard-menu ."

#: admin/wp-security-user-login-menu.php:399
msgid "Login lockout IP whitelist settings"
msgstr ""

#: admin/wp-security-user-login-menu.php:405
msgid "Enable login lockout IP whitelist"
msgstr ""

#: admin/wp-security-user-login-menu.php:416
msgid "The addresses specified here will never be blocked by the login lockout feature."
msgstr ""

#: admin/wp-security-user-login-menu.php:450
msgid "User login feature - Delete all failed login records operation failed."
msgstr "Gebruikersaanmelding feature - Operatie 'verwijder alle mislukte loginrecords' mislukt!"

#: admin/wp-security-user-login-menu.php:452
msgid "All records from the failed logins table were deleted successfully."
msgstr "Alle records uit de lijst mislukte inlogpogingen zijn met succes verwijderd!"

#: admin/wp-security-user-login-menu.php:467
msgid "This tab displays the failed login attempts for your site."
msgstr "Deze tab geeft de mislukte loginpogingen voor jouw site weer."

#: admin/wp-security-user-login-menu.php:468
msgid "The information below can be handy if you need to do security investigations because it will show you the IP range, username and ID (if applicable) and the time/date of the failed login attempt."
msgstr "Onderstaande informatie kan handig zijn om een veiligheidsonderzoek te doen, omdat het IP-bereik, gebruikersnaam en ID (indien van toepassing) en de tijd/datum van de mislukte login poging wordt getoond."

#: admin/wp-security-user-login-menu.php:469
msgid "Failed login records that are older than %1$d days are purged automatically."
msgstr ""

#: admin/wp-security-user-login-menu.php:508
#: admin/wp-security-user-login-menu.php:517
msgid "Delete all failed login records"
msgstr "Verwijder alle mislukte logindata"

#: admin/wp-security-user-login-menu.php:514
msgid "Click this button if you wish to delete all failed login records in one go."
msgstr "Klik deze knop om alle mislukte loginrecords in één keer te verwijderen."

#: admin/wp-security-user-login-menu.php:544
msgid "You entered a non numeric value for the logout time period field. It has been set to the default value."
msgstr "De waarde die je hebt ingevuld is geen nummer. De standaard waarde word nu gebruikt."

#: admin/wp-security-user-login-menu.php:569
msgid "Setting an expiry period for your WP administration session is a simple way to protect against unauthorized access to your site from your computer."
msgstr "Het instellen van een verloop-periode voor de WP-admin-sessie is een simpele manier om je website te beschermen tegen niet toegestane toegang vanaf jouw computer."

#: admin/wp-security-user-login-menu.php:570
msgid "This feature allows you to specify a time period in minutes after which the admin session will expire and the user will be forced to log back in."
msgstr "Deze optie geeft je de mogelijkheid een periode in te stellen waarna de admin-sessies automatisch zullen verlopen en de gebruiker opnieuw moet inloggen."

#: admin/wp-security-user-login-menu.php:575
msgid "Force user logout options"
msgstr "Forceer gebruikeruitlogopties"

#: admin/wp-security-user-login-menu.php:587
msgid "Enable force WP user logout"
msgstr "Aanzetten van geforceerde gebruiker-loguit"

#: admin/wp-security-user-login-menu.php:590
msgid "Check this if you want to force a wp user to be logged out after a configured amount of time"
msgstr "Vink dit aan als je wil dat een gebruik automatisch wordt uitgelogd na een aangegeven tijd"

#: admin/wp-security-user-login-menu.php:594
msgid "Logout the WP user after XX minutes"
msgstr "Log gebruikers uit na XX minuten"

#: admin/wp-security-user-login-menu.php:596
msgid "(Minutes) The user will be forced to log back in after this time period has elapased."
msgstr "(Minuten) De gebruiker wordt gedwongen opnieuw in te loggen na deze periode."

#: admin/wp-security-user-login-menu.php:625
msgid "This tab displays the activity for accounts registered with your site that have logged in using the WordPress login form."
msgstr "Dit tabblad geeft de activiteit aan voor gebruikers die geregistreerd zijn bij uw site, die zijn ingelogd met behulp van het WordPress loginformulier."

#: admin/wp-security-user-login-menu.php:626
msgid "The information below can be handy if you need to do security investigations because it will show you the last 100 recent login events by username, IP address and time/date."
msgstr ""

#: admin/wp-security-user-login-menu.php:627
msgid "Account activity logs that are older than %1$d days are purged automatically."
msgstr ""

#: admin/wp-security-user-login-menu.php:697
msgid "Refresh logged in user data"
msgstr "Vernieuw data ingelogde gebruiker"

#: admin/wp-security-user-login-menu.php:701
msgid "Refresh data"
msgstr "Data verversen"

#: admin/wp-security-user-login-menu.php:706
msgid "This tab displays all users who are currently logged into your site."
msgstr "Deze tab geeft alle gebruikers weer die momenteel zijn ingelogd."

#: admin/wp-security-user-login-menu.php:707
msgid "If you suspect there is a user or users who are logged in which should not be, you can block them by inspecting the IP addresses from the data below and adding them to your blacklist."
msgstr "Als je vermoedt dat een gebruiker is ingelogd terwijl die dat niet hoort te zijn, kan je zijn IP blokkeren door deze op te halen van de data hieronder en die toevoegen aan de blacklist."

#: admin/wp-security-user-login-menu.php:708
msgid "You can also instantly log them out by clicking on the \"Force logout\" link when you hover over the row in the user id column."
msgstr "Je kan ze ook direct uitloggen door te klikken op \"Forceer Uitloggen\" link als je over een rij in de User Id-kolom heengaat."

#: admin/wp-security-user-login-menu.php:713
msgid "Currently logged in users"
msgstr "Momenteel ingelogde gebruikers"

#: admin/wp-security-user-login-menu.php:761
msgid "WordPress 5.6 introduced a new feature  called \"Application passwords\"."
msgstr ""

#: admin/wp-security-user-login-menu.php:762
msgid "This  allows you to create a token from the WordPress dashboard which then can be used in the authorization header."
msgstr ""

#: admin/wp-security-user-login-menu.php:763
msgid "This feature allows you to disable application passwords as they can leave your site vulnerable to social engineering and phishing scams."
msgstr ""

#: admin/wp-security-user-login-menu.php:780
#: classes/grade-system/wp-security-feature-item-manager.php:53
msgid "Disable application password"
msgstr ""

#: admin/wp-security-user-login-menu.php:783
msgid "Check this if you want to disable the application password."
msgstr ""

#: admin/wp-security-user-registration-menu.php:27
msgid "Manual approval"
msgstr "Handmatige goedkeuring"

#: admin/wp-security-user-registration-menu.php:28
#: classes/grade-system/wp-security-feature-item-manager.php:59
msgid "Registration CAPTCHA"
msgstr "Registratie-captcha"

#: admin/wp-security-user-registration-menu.php:29
msgid "Registration honeypot"
msgstr "Registratie honeypot"

#: admin/wp-security-user-registration-menu.php:55
msgid "User registration"
msgstr "Gebruikersregistratie"

#: admin/wp-security-user-registration-menu.php:115
msgid "User registration settings"
msgstr "Instellingen gebruikersregistratie"

#: admin/wp-security-user-registration-menu.php:119
msgid "Manually approve new registrations"
msgstr "Nieuwe registraties handmatig goedkeuren"

#: admin/wp-security-user-registration-menu.php:123
msgid "If your site allows people to create their own accounts via the WordPress registration form, then you can minimize spam or bogus registrations by manually approving each registration."
msgstr "Als uw site mensen in staat stelt om hun eigen account via het WordPress registratieformulier aan te maken, dan kunt u spam of valse registraties minimaliseren door elke registratie handmatig goed te keuren."

#: admin/wp-security-user-registration-menu.php:124
msgid "This feature will automatically set a newly registered account to \"pending\" until the administrator activates it. Therefore undesirable registrants will be unable to log in without your express approval."
msgstr "Met deze functie wordt automatisch een nieuw geregistreerd account ingesteld op \"In behandeling\" totdat de beheerder deze activeert. Ongewenste geregistreerden kunnen daarom niet inloggen zonder uw uitdrukkelijke toestemming."

#: admin/wp-security-user-registration-menu.php:125
msgid "You can view all accounts which have been newly registered via the handy table below and you can also perform bulk activation/deactivation/deletion tasks on each account."
msgstr "U kunt alle accounts bekijken die onlangs via de handige tabel hieronder geregistreerd zijn en je kunt ook bulk activeren / deactiveren / verwijderen van taken op elk account."

#: admin/wp-security-user-registration-menu.php:142
msgid "Enable manual approval of new registrations"
msgstr "Handmatig goedkeuren van nieuwe registraties aanzetten"

#: admin/wp-security-user-registration-menu.php:145
msgid "Check this if you want to automatically disable all newly registered accounts so that you can approve them manually."
msgstr "Vink dit aan als je alle nieuwe gebruikers handmatig wilt controleren."

#: admin/wp-security-user-registration-menu.php:154
msgid "Approve registered users"
msgstr "Goedkeuren geregistreerde gebruikers"

#: admin/wp-security-user-registration-menu.php:206
msgid "This feature allows you to add a CAPTCHA form on the WordPress registration page."
msgstr "Deze optie voegt een captcha form toe aan de WordPress registratiepagina."

#: admin/wp-security-user-registration-menu.php:207
msgid "Users who attempt to register will also need to enter the answer to a simple mathematical question - if they enter the wrong answer, the plugin will not allow them to register."
msgstr "Gebruikers die zich willen registreren zullen antwoord moeten geven op een rekensom - als ze dit fout beantwoorden zullen ze zich niet kunnen registreren."

#: admin/wp-security-user-registration-menu.php:208
msgid "Therefore, adding a CAPTCHA form on the registration page is another effective yet simple spam registration prevention technique."
msgstr "Daarom is het toevoegen van een captcha op de registratiepagina een goede manier om SPAM te voorkomen."

#: admin/wp-security-user-registration-menu.php:212
msgid "Registration page CAPTCHA settings"
msgstr "Registratiepagina captcha-instellingen"

#: admin/wp-security-user-registration-menu.php:219
msgid "The core default behaviour for WordPress Multi Site regarding user registration is that all users are registered via the main site."
msgstr "Het kern standaardgedrag voor WordPress multi-site met betrekking tot registratie als gebruiker is, dat alle gebruikers via de hoofdwebsite geregistreerd worden ."

#: admin/wp-security-user-registration-menu.php:220
msgid "Therefore, if you would like to add a CAPTCHA form to the registration page for a Multi Site, please go to \"Registration CAPTCHA\" settings on the main site."
msgstr "Daarom, als u een CAPTCHA-formulier wilt toe voegen aan de registratiepagina voor een multi-site, ga dan naar de \"registratie CAPTCHA\"-instellingen op de hoofd-site."

#: admin/wp-security-user-registration-menu.php:235
msgid "Enable CAPTCHA on registration page"
msgstr "Captcha op registratiepagina instellen"

#: admin/wp-security-user-registration-menu.php:238
msgid "Check this if you want to insert a CAPTCHA form on the WordPress user registration page (if you allow user registration)."
msgstr "Vink dit aan als je een captcha-formulier wilt weergeven op de WordPress registratiepagina (als je gebruikersregistratie toestaat)"

#: admin/wp-security-user-registration-menu.php:276
msgid "This feature allows you to add a special hidden \"honeypot\" field on the WordPress registration page. This will only be visible to robots and not humans."
msgstr "Deze functie maakt het mogelijk een speciaal verborgen honeypot veld toe te voegen op de WordPress registratiepagina. Dit zal alleen zichtbaar zijn voor robots en niet voor de mens."

#: admin/wp-security-user-registration-menu.php:277
msgid "Since robots usually fill in every input field from a registration form, they will also submit a value for the special hidden honeypot field."
msgstr "Aangezien robots meestal elk invoerveld vullen van een registratieformulier, zullen ze ook een waarde voor het speciale verborgen honeypot-veld sturen."

#: admin/wp-security-user-registration-menu.php:279
msgid "Therefore, if the plugin detects that this field has a value when the registration form is submitted, then the robot which is attempting to register on your site will be redirected to its localhost address - http://127.0.0.1."
msgstr "Daarom, als de plugin detecteert dat dit veld een waarde heeft wanneer het registratieformulier wordt ingediend, dan zal de robot die probeert te registreren op uw site worden doorgestuurd naar het localhost-adres http://127.0.0.1."

#: admin/wp-security-user-registration-menu.php:285
msgid "Registration form honeypot settings"
msgstr "Registratie pagina honeypot-instellingen"

#: admin/wp-security-user-registration-menu.php:296
msgid "Enable honeypot on registration page"
msgstr "Gebruik honeypot op registratiepagina"

#: admin/wp-security-user-registration-menu.php:299
msgid "Check this if you want to enable the honeypot feature for the registration page"
msgstr "Vink dit aan als je gebruik wilt maken van de honeypot-functie op de registratiepagina"

#: classes/aios-ajax.php:89
msgid "Invalid IP retrieve method."
msgstr ""

#: classes/aios-ajax.php:131
#: wp-security-core.php:258
msgid "The security check failed; try refreshing the page."
msgstr ""

#: classes/aios-ajax.php:152
#: wp-security-core.php:268
msgid "You are not allowed to run this command."
msgstr ""

#: classes/aios-ajax.php:173
#: wp-security-core.php:282
msgid "Options can only be saved by network admin"
msgstr ""

#: classes/aios-ajax.php:202
msgid "The command \"%s\" was not found"
msgstr ""

#: classes/grade-system/wp-security-feature-item-manager.php:39
msgid "Remove WP generator meta tag"
msgstr "Verwijder de WP Generator Meta Tag"

#: classes/grade-system/wp-security-feature-item-manager.php:45
msgid "Change display name"
msgstr "Schermnaam wijzigen"

#: classes/grade-system/wp-security-feature-item-manager.php:57
msgid "Registration approval"
msgstr "Goedkeuring registratie"

#: classes/grade-system/wp-security-feature-item-manager.php:61
msgid "Enable registration honeypot"
msgstr "Gebruik registratie-honeypot"

#: classes/grade-system/wp-security-feature-item-manager.php:73
msgid "WordPress files access"
msgstr "WordPress bestandentoegang"

#: classes/grade-system/wp-security-feature-item-manager.php:77
msgid "IP and user agent blacklisting"
msgstr "IP en User Agent Blacklisten"

#: classes/grade-system/wp-security-feature-item-manager.php:81
msgid "Enable basic firewall"
msgstr "Standaard firewall aanzetten"

#: classes/grade-system/wp-security-feature-item-manager.php:82
msgid "Enable pingback vulnerability protection"
msgstr "Pingback-bescherming gebruiken"

#: classes/grade-system/wp-security-feature-item-manager.php:83
msgid "Block accesss to debug log file"
msgstr "Blokkeren toegang tot debug-logbestand"

#: classes/grade-system/wp-security-feature-item-manager.php:87
msgid "Forbid proxy comments"
msgstr "Proxy-reacties verbieden"

#: classes/grade-system/wp-security-feature-item-manager.php:88
msgid "Deny bad queries"
msgstr "Slechte query's blokkeren"

#: classes/grade-system/wp-security-feature-item-manager.php:91
msgid "5G/6G blacklist"
msgstr "5G/6G Blacklist"

#: classes/grade-system/wp-security-feature-item-manager.php:97
msgid "Enable IP blocking for 404 detection"
msgstr "IP-blokkering inschakelen voor 404-detectie"

#: classes/grade-system/wp-security-feature-item-manager.php:101
msgid "Enable rename login page"
msgstr "Hernoemen van loginpagina gebruiken"

#: classes/grade-system/wp-security-feature-item-manager.php:106
msgid "Lost password CAPTCHA"
msgstr "Vergeten wachtwoord Captcha"

#: classes/grade-system/wp-security-feature-item-manager.php:107
msgid "Custom login CAPTCHA"
msgstr "Aangepaste Login Captcha"

#: classes/grade-system/wp-security-feature-item-manager.php:108
msgid "Woo login CAPTCHA"
msgstr "Woo Login Captcha"

#: classes/grade-system/wp-security-feature-item-manager.php:109
msgid "Woo lost password CAPTCHA"
msgstr ""

#: classes/grade-system/wp-security-feature-item-manager.php:110
msgid "Woo register CAPTCHA"
msgstr "Woo Registreer Captcha"

#: classes/grade-system/wp-security-feature-item-manager.php:112
msgid "Login IP whitelisting"
msgstr "Login IP Whitelisten"

#: classes/grade-system/wp-security-feature-item-manager.php:114
msgid "Enable login honeypot"
msgstr "Login-honeypot gebruiken"

#: classes/grade-system/wp-security-feature-item-manager.php:118
msgid "Comment CAPTCHA"
msgstr "Reactie Captcha"

#: classes/grade-system/wp-security-feature-item-manager.php:119
msgid "Block spambots"
msgstr "Spambots blokkeren"

#: classes/grade-system/wp-security-feature-item-manager.php:121
msgid "BuddyPress registration CAPTCHA"
msgstr "BuddyPress Registratie Captcha"

#: classes/grade-system/wp-security-feature-item-manager.php:123
msgid "bbPress new topic CAPTCHA"
msgstr "BBPress Nieuw Topic Captcha"

#: classes/grade-system/wp-security-feature-item.php:29
msgid "Basic"
msgstr "Standaard"

#: classes/grade-system/wp-security-feature-item.php:31
msgid "Intermediate"
msgstr "Tussentijds"

#: classes/grade-system/wp-security-feature-item.php:33
msgid "Advanced"
msgstr "Geavanceerd"

#: classes/wp-security-captcha.php:47
#: classes/wp-security-general-init-tasks.php:407
msgid "Please enter an answer in digits:"
msgstr "Vul een antwoord in in cijfers:"

#: classes/wp-security-captcha.php:127
msgid "one"
msgstr "een"

#: classes/wp-security-captcha.php:128
msgid "two"
msgstr "twee"

#: classes/wp-security-captcha.php:129
msgid "three"
msgstr "drie"

#: classes/wp-security-captcha.php:130
msgid "four"
msgstr "vier"

#: classes/wp-security-captcha.php:131
msgid "five"
msgstr "vijf"

#: classes/wp-security-captcha.php:132
msgid "six"
msgstr "zes"

#: classes/wp-security-captcha.php:133
msgid "seven"
msgstr "zeven"

#: classes/wp-security-captcha.php:134
msgid "eight"
msgstr "acht"

#: classes/wp-security-captcha.php:135
msgid "nine"
msgstr "negen"

#: classes/wp-security-captcha.php:136
msgid "ten"
msgstr "tien"

#: classes/wp-security-captcha.php:137
msgid "eleven"
msgstr "elf"

#: classes/wp-security-captcha.php:138
msgid "twelve"
msgstr "twaalf"

#: classes/wp-security-captcha.php:139
msgid "thirteen"
msgstr "dertien"

#: classes/wp-security-captcha.php:140
msgid "fourteen"
msgstr "veertien"

#: classes/wp-security-captcha.php:141
msgid "fifteen"
msgstr "vijftien"

#: classes/wp-security-captcha.php:142
msgid "sixteen"
msgstr "zestien"

#: classes/wp-security-captcha.php:143
msgid "seventeen"
msgstr "zeventien"

#: classes/wp-security-captcha.php:144
msgid "eighteen"
msgstr "achttien"

#: classes/wp-security-captcha.php:145
msgid "nineteen"
msgstr "negentien"

#: classes/wp-security-captcha.php:146
msgid "twenty"
msgstr "twintig"

#: classes/wp-security-cronjob-handler.php:34
msgid "Every 15 minutes"
msgstr ""

#: classes/wp-security-debug-logger.php:46
msgid "Unable to get the reason why"
msgstr ""

#: classes/wp-security-debug-logger.php:47
msgid "Unable to clear the logs"
msgstr ""

#: classes/wp-security-file-scan.php:85
msgid "All In One WP Security - File change detected!"
msgstr "All In One WP Security - Gewijzigd bestand gevonden!"

#: classes/wp-security-file-scan.php:87
msgid "A file change was detected on your system for site URL"
msgstr "Een bestandswijziging is gevonden op jouw systeem voor site-URL"

#: classes/wp-security-file-scan.php:87
msgid ". Scan was generated on"
msgstr "Gescand op"

#: classes/wp-security-file-scan.php:88
msgid "A summary of the scan results is shown below:"
msgstr "Een samenvatting van de scan staat hieronder:"

#: classes/wp-security-file-scan.php:91
msgid "Login to your site to view the scan details."
msgstr "Login in op uw website om de scan te bekijken."

#: classes/wp-security-file-scan.php:313
msgid "The following files were added to your host"
msgstr "De volgende bestanden zijn toegevoegd aan je host"

#: classes/wp-security-file-scan.php:315
#: classes/wp-security-file-scan.php:323
#: classes/wp-security-file-scan.php:332
msgid "modified on: "
msgstr "bewerkt op: "

#: classes/wp-security-file-scan.php:321
msgid "The following files were removed from your host"
msgstr "De volgende regels zijn verwijderd van jouw host"

#: classes/wp-security-file-scan.php:330
msgid "The following files were changed on your host"
msgstr "De volgende regels zijn bewerkt op jouw host"

#: classes/wp-security-general-init-tasks.php:212
#: classes/wp-security-general-init-tasks.php:481
msgid "Application passwords have been disabled by All In One WP Security & Firewall plugin."
msgstr ""

#: classes/wp-security-general-init-tasks.php:428
#: classes/wp-security-general-init-tasks.php:541
#: classes/wp-security-general-init-tasks.php:574
#: classes/wp-security-user-login.php:137
#: classes/wp-security-user-registration.php:74
msgid "<strong>ERROR</strong>: Your answer was incorrect - please try again."
msgstr "<strong>FOUT</strong>: Je antwoord was niet goed - probeer opnieuw."

#: classes/wp-security-general-init-tasks.php:463
msgid "Enter something special:"
msgstr "Vul iets speciaals in:"

#: classes/wp-security-general-init-tasks.php:476
msgid "Application passwords"
msgstr ""

#: classes/wp-security-general-init-tasks.php:485
msgid "Change setting"
msgstr ""

#: classes/wp-security-general-init-tasks.php:487
msgid "Site admin can only change this setting."
msgstr ""

#: classes/wp-security-general-init-tasks.php:516
msgid "Error: You entered an incorrect CAPTCHA answer. Please go back and try again."
msgstr "Fout: Je hebt een fout CAPTCHA-antwoord gegeven. Probeer opnieuw."

#: classes/wp-security-general-init-tasks.php:558
msgid "Your CAPTCHA answer was incorrect - please try again."
msgstr "JE CAPTCHA-antwoord was fout - probeer opnieuw."

#: classes/wp-security-general-init-tasks.php:567
msgid "<strong>ERROR</strong>: Your IP address is currently locked please contact the administrator!"
msgstr ""

#. translators: %s: Admin Dashboard > WP Security > Brute Force > Login CAPTCHA Tab Link
#: classes/wp-security-general-init-tasks.php:642
msgid "Your Google reCAPTCHA site key is wrong. Please fill the correct reCAPTCHA keys %s to use the Google reCAPTCHA feature."
msgstr ""

#. translators: %s: Admin Dashboard > WP Security > Brute Force > Login CAPTCHA Tab Link
#: classes/wp-security-general-init-tasks.php:642
#: classes/wp-security-notices.php:99
msgid "here"
msgstr ""

#: classes/wp-security-general-init-tasks.php:655
msgid "Would you like All In One WP Security & Firewall to re-insert the security rules in your .htaccess file which were cleared when you deactivated the plugin?"
msgstr "Wilt u dat All In One WP Security & Firewall de beveiligingsregels in uw .htaccess-bestand opnieuw invoegt die werden gewist toen u de plug-in deactiveerde ?"

#: classes/wp-security-general-init-tasks.php:655
#: templates/may-also-like.php:40
#: templates/may-also-like.php:43
#: templates/may-also-like.php:54
#: templates/may-also-like.php:57
#: templates/may-also-like.php:68
#: templates/may-also-like.php:71
#: templates/may-also-like.php:91
#: templates/may-also-like.php:103
#: templates/may-also-like.php:115
#: templates/may-also-like.php:127
#: templates/may-also-like.php:139
#: templates/may-also-like.php:151
#: templates/may-also-like.php:168
#: templates/may-also-like.php:171
#: templates/may-also-like.php:183
#: templates/may-also-like.php:195
#: templates/may-also-like.php:207
#: templates/may-also-like.php:219
#: templates/may-also-like.php:231
#: templates/may-also-like.php:243
#: templates/may-also-like.php:252
#: templates/may-also-like.php:255
#: templates/may-also-like.php:264
#: templates/may-also-like.php:267
#: templates/may-also-like.php:279
#: templates/may-also-like.php:297
#: templates/may-also-like.php:309
#: templates/may-also-like.php:327
#: templates/may-also-like.php:339
#: templates/may-also-like.php:351
#: templates/may-also-like.php:368
#: templates/may-also-like.php:380
msgid "Yes"
msgstr ""

#: classes/wp-security-general-init-tasks.php:655
#: templates/may-also-like.php:88
#: templates/may-also-like.php:100
#: templates/may-also-like.php:112
#: templates/may-also-like.php:124
#: templates/may-also-like.php:136
#: templates/may-also-like.php:148
#: templates/may-also-like.php:180
#: templates/may-also-like.php:192
#: templates/may-also-like.php:204
#: templates/may-also-like.php:216
#: templates/may-also-like.php:228
#: templates/may-also-like.php:240
#: templates/may-also-like.php:276
#: templates/may-also-like.php:294
#: templates/may-also-like.php:306
#: templates/may-also-like.php:324
#: templates/may-also-like.php:336
#: templates/may-also-like.php:348
#: templates/may-also-like.php:365
#: templates/may-also-like.php:377
#: templates/notices/custom-notice.php:27
msgid "No"
msgstr ""

#: classes/wp-security-general-init-tasks.php:674
msgid "Your registration is pending approval."
msgstr "Je registratie wacht nog op goedkeuring."

#: classes/wp-security-notices.php:25
msgid "The All in One Security plugin has disabled the login whitelist setting that you have enabled in the past."
msgstr ""

#: classes/wp-security-notices.php:29
msgid "Your website is running on an Apache webserver, the login whitelisting might not be functional until the recent update of AIOS (because it relied upon Apache-specific module features)."
msgstr ""

#: classes/wp-security-notices.php:31
msgid "Your website is running on a non-Apache webserver, so the login whitelisting was not functional until the recent update of AIOS (because it relied upon Apache-specific features)."
msgstr ""

#: classes/wp-security-notices.php:33
msgid "It began working with AIOS version 5.0.8."
msgstr ""

#: classes/wp-security-notices.php:33
msgid "We have disabled it so that your login page will not be blocked unexpectedly."
msgstr ""

#: classes/wp-security-notices.php:42
msgid "Would you like to re-enable login whitelisting?"
msgstr ""

#: classes/wp-security-notices.php:48
msgid "Removed database backup feature from the All In One WP Security & Firewall plugin"
msgstr ""

#: classes/wp-security-notices.php:50
msgid "Beginning with version 5.0.0, AIOS has replaced the AIOS backup method with the superior UpdraftPlus method."
msgstr ""

#: classes/wp-security-notices.php:51
msgid "It remains free and is fully supported by the UpdraftPlus team."
msgstr ""

#: classes/wp-security-notices.php:54
msgid "You are seeing this notice because you have previously set up automated database backups in AIOS."
msgstr ""

#: classes/wp-security-notices.php:55
msgid "Would you like to set up scheduled backups with UpdraftPlus?"
msgstr ""

#: classes/wp-security-notices.php:61
msgid "Setup UpdraftPlus backup plugin"
msgstr ""

#: classes/wp-security-notices.php:67
msgid "Important: set up your IP address detection settings"
msgstr ""

#: classes/wp-security-notices.php:69
msgid "The All in One Security plugin couldn't be certain about the correct method to detect the IP address for your site visitors with your currently-configured IP address detection settings."
msgstr ""

#: classes/wp-security-notices.php:70
msgid "It is important for your security to set the IP address detection settings properly."
msgstr ""

#: classes/wp-security-notices.php:73
msgid "Please go to the settings and set them now."
msgstr ""

#: classes/wp-security-notices.php:79
msgid "Setup IP address detection settings"
msgstr ""

#: classes/wp-security-notices.php:85
msgid "Important: Disabled login whitelist setting"
msgstr ""

#: classes/wp-security-notices.php:91
msgid "Turn it back on"
msgstr ""

#: classes/wp-security-notices.php:92
msgid "Edit the settings"
msgstr ""

#: classes/wp-security-notices.php:95
msgid "Keep it off"
msgstr ""

#: classes/wp-security-notices.php:99
msgid "Hey - We noticed All In One WP Security & Firewall has kept your site safe for a while.  If you like us, please consider leaving a positive review to spread the word.  Or if you have any issues or questions please leave us a support message %s."
msgstr ""

#: classes/wp-security-notices.php:99
msgid "Thank you so much!"
msgstr ""

#: classes/wp-security-notices.php:99
msgid "Team All In One WP Security & Firewall"
msgstr ""

#: classes/wp-security-notices.php:109
msgid "Enhance your security even more by backing up your site"
msgstr ""

#: classes/wp-security-notices.php:110
msgid "UpdraftPlus is the world's most trusted backup plugin from the owners of All In One WP Security & Firewall"
msgstr ""

#: classes/wp-security-notices.php:121
msgid "After you've secured your site, we recommend you install our WP-Optimize plugin to streamline it for better website performance."
msgstr ""

#: classes/wp-security-process-renamed-login-page.php:152
msgid "Not available."
msgstr "Niet beschikbaar."

#: classes/wp-security-two-factor-login.php:34
msgid "Two factor authentication - Admin settings"
msgstr ""

#: classes/wp-security-two-factor-login.php:97
msgid "Two Factor Auth"
msgstr ""

#: classes/wp-security-two-factor-login.php:153
msgid "PHP OpenSSL or mcrypt module required"
msgstr ""

#: classes/wp-security-two-factor-login.php:153
msgid "The All In One WP Security plugin's Two Factor Authentication module requires either the PHP openssl (preferred) or mcrypt module to be installed. Please ask your web hosting company to install one of them."
msgstr ""

#: classes/wp-security-user-login.php:71
msgid "You have disabled login lockout by defining the AIOS_DISABLE_LOGIN_LOCKOUT constant value as true, and the login lockout setting has enabled it."
msgstr ""

#. translators: 1: Locked IP Addresses admin page link
#: classes/wp-security-user-login.php:73
msgid "Delete your login lockout IP from %s and define the AIOS_DISABLE_LOGIN_LOCKOUT constant value as false."
msgstr ""

#: classes/wp-security-user-login.php:100
msgid "<strong>ERROR</strong>: Access from your IP address has been blocked for security reasons. Please contact the administrator."
msgstr "<strong>Fout</strong>: Toegang van jouw IP-adres is geblokkeerd om veiligheidsredenen. Neem contact op met de beheerder."

#: classes/wp-security-user-login.php:108
msgid "Service temporarily unavailable"
msgstr "Service tijdelijk niet beschikbaar"

#: classes/wp-security-user-login.php:163
msgid "<strong>ACCOUNT PENDING</strong>: Your account is currently not active. An administrator needs to activate your account before you can login."
msgstr "<strong>ACCOUNT PENDING</strong>: Jouw account is momenteel niet actief. Een administrator moet jouw account eerst activeren voordat je kan inloggen."

#: classes/wp-security-user-login.php:242
msgid "<strong>ERROR</strong>: Invalid login credentials."
msgstr "<strong>FOUT</strong>: Verkeerde logingegevens."

#: classes/wp-security-user-login.php:392
msgid "Site Lockout Notification"
msgstr "Melding siteblokkade"

#: classes/wp-security-user-login.php:393
msgid "User login lockout events had occurred due to too many failed login attempts or invalid username:"
msgstr ""

#: classes/wp-security-user-login.php:396
msgid "Username:"
msgstr "Gebruikersnaam:"

#: classes/wp-security-user-login.php:397
msgid "IP address:"
msgstr "IP Adres:"

#: classes/wp-security-user-login.php:399
msgid "IP range:"
msgstr "IP Bereik:"

#: classes/wp-security-user-login.php:404
msgid "Log into your site WordPress administration panel to see the duration of the lockout or to unlock the user."
msgstr ""

#: classes/wp-security-user-login.php:515
msgid "Unlock request notification"
msgstr "Melding aanvraag deblokkade"

#: classes/wp-security-user-login.php:516
msgid "You have requested for the account with email address %s to be unlocked. Please click the link below to unlock your account:"
msgstr "Je hebt gevraagd het account met e-mailadres %s te deblokkeren. Klik op de onderstaande link om je account te deblokkeren:"

#: classes/wp-security-user-login.php:516
msgid "Unlock link: %s"
msgstr "Ontgrendel link: %s"

#: classes/wp-security-user-login.php:516
msgid "After clicking the above link you will be able to login to the WordPress administration panel."
msgstr "Nadat u op de bovenstaande link hebt geklikt, kunt u inloggen op het WordPress-beheerpaneel ."

#: classes/wp-security-user-login.php:739
msgid "Your session has expired because it has been over %d minutes since your last login."
msgstr "Je sessie is verlopen omdat het al langer dan %d minuten geleden is sinds je voor het laatst bent ingelogd."

#: classes/wp-security-user-login.php:740
#: classes/wp-security-user-login.php:744
msgid "Please log back in to continue."
msgstr "Log weer in om verder te gaan."

#: classes/wp-security-user-login.php:743
msgid "You were logged out because you just changed the \"admin\" username."
msgstr "Je bent uitgelogd omdat je de \"admin\"-gebruikersnaam hebt veranderd."

#: classes/wp-security-user-login.php:773
msgid "Request unlock"
msgstr "Deblokkade aanvragen"

#: classes/wp-security-user-registration.php:68
msgid "<strong>ERROR</strong>: You are not allowed to register because your IP address is currently locked!"
msgstr "<strong>ERROR</strong>: Je kan nu niet registreren omdat jouw IP-adres geblokkeerd is!"

#: classes/wp-security-utility-ip-address.php:217
#: classes/wp-security-utility-ip-address.php:231
#: classes/wp-security-utility-ip-address.php:245
#: classes/wp-security-utility-ip-address.php:257
#: classes/wp-security-utility-ip-address.php:269
msgid " is not a valid ip address format."
msgstr " is geen geldig IP-adres."

#: classes/wp-security-utility-ip-address.php:274
msgid "You cannot ban your own IP address: "
msgstr "Je kan je eigen IP-adres niet blokkeren: "

#: classes/wp-security-utility.php:254
msgid "This feature can only be configured by the \"superadmin\" on the main site."
msgstr "Deze optie kan alleen geconfigureerd worden door de \"superadmin\" op de hoofdsite."

#: other-includes/wp-security-unlock-request.php:32
msgid "ERROR: Unable to process your request!"
msgstr "FOUT : kan uw aanvraag niet verwerken !"

#: other-includes/wp-security-unlock-request.php:45
msgid "Please enter a valid email address"
msgstr "Vul alsjeblieft een geldig e-mailadres in"

#: other-includes/wp-security-unlock-request.php:57
msgid "User account not found!"
msgstr "Gebruikersaccount niet gevonden!"

#: other-includes/wp-security-unlock-request.php:71
msgid "Error: No locked entry was found in the database with your IP address range."
msgstr "Fout : er is geen vergrendelde invoer gevonden in de database met uw IP-adresbereik!"

#: other-includes/wp-security-unlock-request.php:76
msgid "An email has been sent to you with the unlock instructions."
msgstr "Een e-mail is naar je onderweg met instructies om jezelf te ontgrendelen."

#: other-includes/wp-security-unlock-request.php:93
msgid "You are here because you have been locked out due to too many incorrect login attempts."
msgstr "Je bent hier omdat je geblokkeerd bent wegens te vaak proberen in te loggen met verkeerde gegevens."

#: other-includes/wp-security-unlock-request.php:94
msgid "Please enter your email address and you will receive an email with instructions on how to unlock yourself."
msgstr "Vul a.u.b. jouw e-mailadres in en je zal een e-mail ontvangen met instructies om jezelf te ontgrendelen."

#: other-includes/wp-security-unlock-request.php:104
msgid "Email Address"
msgstr "E-mailadres"

#: other-includes/wp-security-unlock-request.php:108
msgid "Send unlock request"
msgstr "Verstuur ontgrendelaanvraag"

#: templates/admin/incompatible-plugin.php:6
msgid "Two Factor Authentication"
msgstr ""

#: templates/admin/incompatible-plugin.php:10
msgid "Two Factor Authentication currently disabled"
msgstr ""

#: templates/admin/incompatible-plugin.php:12
#: templates/admin/incompatible-plugin.php:16
msgid "Two factor authentication in All In One WP Security is currently disabled because the incompatible plugin %s is active."
msgstr ""

#: templates/automated-database-backup.php:4
msgid "Automated scheduled backups"
msgstr "Ingeplande back-ups"

#: templates/automated-database-backup.php:9
msgid "Automate backup in the UpdraftPlus plugin"
msgstr ""

#: templates/automated-database-backup.php:19
msgid "The AIOS 5.0.0 version release has removed the automated backup feature."
msgstr ""

#: templates/automated-database-backup.php:20
msgid "The AIOS automated backup had issues that made it less robust than we could be happy with."
msgstr ""

#: templates/automated-database-backup.php:21
msgid "Follow this link to automate backups in the superior UpdraftPlus backup plugin."
msgstr ""

#: templates/info/ip-address-ip-range-info.php:5
msgid "Each IP address must be on a new line."
msgstr "Elke IP-adres moet beginnen op een nieuwe regel."

#: templates/info/ip-address-ip-range-info.php:6
msgid "To specify an IPv4 range use a wildcard \"*\" character. Acceptable ways to use wildcards is shown in the examples below:"
msgstr "Gebruik een jokerteken \"*\" om een IPv4-bereik op te geven. Aanvaardbare manieren om jokertekens te gebruiken worden weergegeven in de onderstaande voorbeelden:"

#: templates/info/ip-address-ip-range-info.php:7
msgid "Example 1: 195.47.89.*"
msgstr "Voorbeeld 1: 195.47.89.*"

#: templates/info/ip-address-ip-range-info.php:8
msgid "Example 2: 195.47.*.*"
msgstr "Voorbeeld 2: 195.47.*.*"

#: templates/info/ip-address-ip-range-info.php:9
msgid "Example 3: 195.*.*.*"
msgstr "Voorbeeld 3: 195.*.*.*"

#: templates/info/ip-address-ip-range-info.php:10
msgid "To specify an IPv6 range use CIDR format as shown in the examples below:"
msgstr ""

#: templates/info/ip-address-ip-range-info.php:11
msgid "Example 4: 2401:4900:54c3:af15:2:2:5dc0:0/112"
msgstr ""

#: templates/info/ip-address-ip-range-info.php:12
msgid "Example 5: 2001:db8:1263::/48"
msgstr ""

#: templates/may-also-like.php:5
msgid "All-In-One Security (AIOS) Free vs Premium Comparison Chart"
msgstr ""

#: templates/may-also-like.php:7
msgid "FAQs"
msgstr ""

#: templates/may-also-like.php:9
msgid "Ask a pre-sales question"
msgstr ""

#: templates/may-also-like.php:17
msgid "All In One WP Security & Firewall Free"
msgstr ""

#: templates/may-also-like.php:26
#: templates/may-also-like.php:386
msgid "Installed"
msgstr ""

#: templates/may-also-like.php:29
#: templates/may-also-like.php:389
msgid "Upgrade now"
msgstr ""

#: templates/may-also-like.php:34
msgid "Login security feature suite"
msgstr ""

#: templates/may-also-like.php:35
msgid "Protect against brute-force attacks and keep bots at bay."
msgstr ""

#: templates/may-also-like.php:35
msgid "AIOS takes WordPress' default login security features to a whole new level."
msgstr ""

#: templates/may-also-like.php:37
msgid "To see all login security features, visit %s"
msgstr ""

#: templates/may-also-like.php:48
msgid "Firewall and file protection feature suite"
msgstr ""

#: templates/may-also-like.php:49
msgid "Protection from the latest exploits."
msgstr ""

#: templates/may-also-like.php:49
msgid "Activate firewall settings ranging from basic, intermediate and advanced."
msgstr ""

#: templates/may-also-like.php:49
msgid "Get comprehensive, instant protection with All-in-One Security."
msgstr ""

#: templates/may-also-like.php:51
msgid "To see all firewall and file protection features, visit %s"
msgstr ""

#: templates/may-also-like.php:62
msgid "Content protection feature suite"
msgstr ""

#: templates/may-also-like.php:63
msgid "Eliminate spam and protect your content to dramatically improve your website's interactions with search engines."
msgstr ""

#: templates/may-also-like.php:65
msgid "To see all content protection features, visit %s"
msgstr ""

#: templates/may-also-like.php:76
msgid "Malware scanning"
msgstr ""

#: templates/may-also-like.php:77
msgid "Finding out by accident that your site has been infected with malware is too late."
msgstr ""

#: templates/may-also-like.php:79
msgid "Malware can have a dramatic effect on your site's search rankings and you may not even know about it."
msgstr ""

#: templates/may-also-like.php:79
msgid "It can slow your website down, access customer data, send unsolicited emails, change your content or prevent users from accessing it."
msgstr ""

#: templates/may-also-like.php:84
msgid "Automatic malware scanning"
msgstr ""

#: templates/may-also-like.php:85
msgid "Best-in-class scanning for the latest malware, trojans and spyware 24/7."
msgstr ""

#: templates/may-also-like.php:96
msgid "Response time monitoring"
msgstr ""

#: templates/may-also-like.php:97
msgid "You'll know immediately if your website's response time is negatively affected."
msgstr ""

#: templates/may-also-like.php:108
msgid "Up-time monitoring"
msgstr ""

#: templates/may-also-like.php:109
msgid "AIOS checks your website's uptime every 5 minutes."
msgstr ""

#: templates/may-also-like.php:109
msgid "We'll notify you straight away if your site/server goes down."
msgstr ""

#: templates/may-also-like.php:120
msgid "Prevents blacklisting by search engines"
msgstr ""

#: templates/may-also-like.php:121
msgid "AIOS monitors your site's blacklist status daily."
msgstr ""

#: templates/may-also-like.php:121
msgid "We'll notify you within 24 hours if something's amiss so you can take action, before it's too late."
msgstr ""

#: templates/may-also-like.php:132
msgid "Flexible assignment"
msgstr ""

#: templates/may-also-like.php:133
msgid "Register and remove websites from the scanning service at any time."
msgstr ""

#: templates/may-also-like.php:144
msgid "Malware reports"
msgstr ""

#: templates/may-also-like.php:145
msgid "Reports are available via the 'My Account' page and directly via email."
msgstr ""

#: templates/may-also-like.php:156
msgid "Flexible two-factor authentication"
msgstr ""

#: templates/may-also-like.php:157
msgid "With Two-Factor Authentication (TFA) users enter their username and password and a one-time code sent to a device to login."
msgstr ""

#: templates/may-also-like.php:159
msgid "TFA is a feature in both our free and premium packages, but AIOS Premium affords whole new levels of control over how TFA is implemented."
msgstr ""

#: templates/may-also-like.php:164
msgid "Authenticator apps"
msgstr ""

#: templates/may-also-like.php:165
msgid "Supports TOTP and HOTP protocols."
msgstr ""

#: templates/may-also-like.php:165
msgid "TFA Can be used with Google Authenticator, Microsoft Authenticator, Authy and many more."
msgstr ""

#: templates/may-also-like.php:176
msgid "Role specific configuration"
msgstr ""

#: templates/may-also-like.php:177
msgid "Make it compulsory for certain roles e.g. for admin and editor roles."
msgstr ""

#: templates/may-also-like.php:188
msgid "Require TFA after a set time period"
msgstr ""

#: templates/may-also-like.php:189
msgid "For example you could require all admins to have TFA once their accounts are a week old."
msgstr ""

#: templates/may-also-like.php:200
msgid "Trusted devices - control how often TFA is required"
msgstr ""

#: templates/may-also-like.php:201
msgid "Ask for TFA after a chosen number of days for trusted devices instead of on every login."
msgstr ""

#: templates/may-also-like.php:212
msgid "Anti-bot protection"
msgstr ""

#: templates/may-also-like.php:213
msgid "Option to hide the existence of forms on WooCommerce login pages unless JavaScript is active."
msgstr ""

#: templates/may-also-like.php:224
msgid "Customise TFA design layout"
msgstr ""

#: templates/may-also-like.php:225
msgid "Customise the design of TFA so it aligns with your existing web design."
msgstr ""

#: templates/may-also-like.php:236
msgid "TFA emergency codes"
msgstr ""

#: templates/may-also-like.php:237
msgid "Generate a one-time use emergency code to allow access if your device is lost."
msgstr ""

#: templates/may-also-like.php:248
msgid "TFA multisite compatibility"
msgstr ""

#: templates/may-also-like.php:249
msgid "TFA is Compatible with multisite networks and sub-sites."
msgstr ""

#: templates/may-also-like.php:260
msgid "TFA support for common login forms"
msgstr ""

#: templates/may-also-like.php:261
msgid "Supports WooCommerce, Affiliates-WP and Theme my Login login forms."
msgstr ""

#: templates/may-also-like.php:272
msgid "TFA support for other login forms"
msgstr ""

#: templates/may-also-like.php:273
msgid "Supports Elementor Pro, bbPress and all third-party login forms without any further coding needed."
msgstr ""

#: templates/may-also-like.php:284
msgid "Smart 404 blocking"
msgstr ""

#: templates/may-also-like.php:285
msgid "404 errors can occur when someone legitimately mistypes a URL, but they're also generated by hackers searching for weaknesses in your site."
msgstr ""

#: templates/may-also-like.php:290
msgid "Automatically and permanently blocks bots producing 404s"
msgstr ""

#: templates/may-also-like.php:291
msgid "AIOS Premium provides more protection than the competition by automatically and permanently blocking IP addresses of bots and hackers based on how many 404 errors they generate."
msgstr ""

#: templates/may-also-like.php:302
msgid "404 error charts"
msgstr ""

#: templates/may-also-like.php:303
msgid "Handy charts keep you informed of how many 404s have occurred and which IP address or country is producing them."
msgstr ""

#: templates/may-also-like.php:314
msgid "Country blocking"
msgstr ""

#: templates/may-also-like.php:315
msgid "Most malicious attacks come from a handful of countries and so it's possible to prevent most attacks with our country blocking tool."
msgstr ""

#: templates/may-also-like.php:320
msgid "Block traffic based on country of origin"
msgstr ""

#: templates/may-also-like.php:321
msgid "AIOS Premium utilises an IP database that promises 99.5% accuracy."
msgstr ""

#: templates/may-also-like.php:332
msgid "Block traffic to specific pages based on country of origin"
msgstr ""

#: templates/may-also-like.php:333
msgid "Block access to your whole site or on a page-by-page basis."
msgstr ""

#: templates/may-also-like.php:344
msgid "Whitelist some users from blocked countries"
msgstr ""

#: templates/may-also-like.php:345
msgid "Whitelist IP addresses or IP ranges even if they are part of a blocked country."
msgstr ""

#: templates/may-also-like.php:356
msgid "Premium support"
msgstr ""

#: templates/may-also-like.php:361
msgid "Unlimited support"
msgstr ""

#: templates/may-also-like.php:362
msgid "Personalised, email support from our team of Security experts, as and when you need it."
msgstr ""

#: templates/may-also-like.php:373
msgid "Guaranteed response time"
msgstr ""

#: templates/may-also-like.php:374
msgid "We offer a guaranteed response time of three days."
msgstr ""

#: templates/may-also-like.php:374
msgid "99% of our Premium customers receive a response to their enquiry within 24 hours during the working week."
msgstr ""

#: templates/may-also-like.php:397
msgid "Our other plugins"
msgstr ""

#: templates/may-also-like.php:411
msgid "UpdraftPlus – the ultimate protection for your site, hard work and business"
msgstr ""

#: templates/may-also-like.php:412
msgid "Simplifies backups and restoration."
msgstr ""

#: templates/may-also-like.php:412
msgid "It is the world's highest ranking and most popular scheduled backup plugin, with over three million currently-active installs."
msgstr ""

#: templates/may-also-like.php:413
#: templates/may-also-like.php:419
#: templates/may-also-like.php:425
#: templates/may-also-like.php:431
msgid "Try for free"
msgstr ""

#: templates/may-also-like.php:417
msgid "WP-Optimize – keep your database fast and efficient"
msgstr ""

#: templates/may-also-like.php:418
msgid "Makes your site fast and efficient."
msgstr ""

#: templates/may-also-like.php:418
msgid "It cleans the database, compresses images and caches pages for ultimate speed."
msgstr ""

#: templates/may-also-like.php:423
msgid "UpdraftCentral – save hours managing multiple WP sites from one place"
msgstr ""

#: templates/may-also-like.php:424
msgid "Highly efficient way to manage, optimize, update and backup multiple websites from one place."
msgstr ""

#: templates/may-also-like.php:429
msgid "Easy Updates Manager"
msgstr ""

#: templates/may-also-like.php:430
msgid "Keeps your WordPress site up to date and bug free."
msgstr ""

#: templates/menus/settings/advanced-settings.php:2
msgid "IP address detection settings"
msgstr ""

#: templates/menus/settings/advanced-settings.php:6
msgid "The IP address detection settings allow you to specify how visitors' IP addresses are made known to PHP (and hence to WordPress and its plugins)."
msgstr ""

#: templates/menus/settings/advanced-settings.php:7
msgid "Usually, this is automatic and there is only one choice."
msgstr ""

#: templates/menus/settings/advanced-settings.php:8
msgid "However in some setups, such as those using proxies (including load-balancers and security firewalls like Cloudflare), it may be necessary to set this manually."
msgstr ""

#: templates/menus/settings/advanced-settings.php:9
msgid "Attention"
msgstr "Attentie!"

#: templates/menus/settings/advanced-settings.php:9
msgid "It is important to set this correctly - otherwise you may make it possible for a hacker to ban all your visitors (e.g. via banning Cloudflare from connecting to you) instead of being banned himself."
msgstr ""

#: templates/menus/settings/advanced-settings.php:9
msgid "The default is to use the REMOTE_ADDR PHP server variable. If this variable does not contain the visitor's IP address, then whilst you can make a different selection below, it is better to ask your web hosting company to have it correctly set."
msgstr ""

#: templates/menus/settings/advanced-settings.php:10
msgid "This is the most secure setup, because when set correctly it is immune from being spoofed by an attacker."
msgstr ""

#: templates/menus/settings/advanced-settings.php:16
msgid "You have no available IP address detection method(s); you must contact your web hosting company."
msgstr ""

#: templates/menus/settings/advanced-settings.php:22
#: templates/menus/settings/advanced-settings.php:27
#: templates/menus/settings/advanced-settings.php:32
msgid "Your detected IP address according to %s:"
msgstr ""

#: templates/menus/settings/advanced-settings.php:38
msgid "If your site is setup on localhost, you won't see your external IP address using your server's IP detection setting; but on a localhost-served site (not available to the outside world), the setting is irrelevant and can be ignored."
msgstr ""

#: templates/menus/settings/advanced-settings.php:61
msgid "Choose a $_SERVER variable you would like to detect visitors' IP address using."
msgstr ""

#: templates/menus/settings/advanced-settings.php:67
msgid "If your chosen server variable fails the plugin will automatically fall back to retrieving the IP address from $_SERVER[\"REMOTE_ADDR\"]"
msgstr "Als de door u gekozen servervariabele niet werkt, zal de plug- in automatisch terugvallen op het ophalen van het IP-adres van $ _SERVER [\"REMOTE_ADDR\"]"

#: templates/menus/settings/advanced-settings.php:73
msgid "Your IP address if using this setting:"
msgstr ""

#: templates/menus/settings/advanced-settings.php:75
msgid "fetching..."
msgstr ""

#: templates/menus/settings/advanced-settings.php:81
#: templates/menus/settings/advanced-settings.php:190
msgid "getting..."
msgstr ""

#: templates/menus/settings/advanced-settings.php:89
msgid "look-up possibly blocked by an ad-blocker or similar tool"
msgstr ""

#: templates/notices/cookie-based-brute-force-prevention-disabled.php:4
msgid "Cookie based brute force login prevention currently disabled"
msgstr ""

#: templates/notices/cookie-based-brute-force-prevention-disabled.php:6
msgid "Cookie based brute force login prevention is currently disabled via the AIOS_DISABLE_COOKIE_BRUTE_FORCE_PREVENTION constant (which is mostly likely to be defined in your wp-config.php)"
msgstr ""

#: templates/notices/disable-login-whitelist.php:4
msgid "Login whitelisting currently disabled"
msgstr ""

#: templates/notices/disable-login-whitelist.php:6
msgid "Login whitelisting is currently disabled via the AIOS_DISABLE_LOGIN_WHITELIST constant (which is mostly likely to be defined in your wp-config.php)"
msgstr ""

#: templates/notices/horizontal-notice.php:8
#: templates/notices/horizontal-notice.php:40
msgid "notice image"
msgstr ""

#: templates/notices/horizontal-notice.php:18
msgid "Ok, you deserve it"
msgstr ""

#: templates/notices/horizontal-notice.php:22
msgid "Maybe later"
msgstr ""

#: templates/notices/horizontal-notice.php:26
msgid "Never"
msgstr ""

#: templates/notices/horizontal-notice.php:66
msgid "Get UpdraftCentral"
msgstr ""

#: templates/notices/horizontal-notice.php:68
msgid "Get UpdraftPlus"
msgstr ""

#: templates/notices/horizontal-notice.php:70
msgid "Get WP-Optimize"
msgstr ""

#: templates/notices/horizontal-notice.php:72
msgid "Find out more."
msgstr ""

#: templates/notices/horizontal-notice.php:74
msgid "Sign up"
msgstr ""

#: templates/notices/horizontal-notice.php:76
msgid "Go there"
msgstr ""

#: templates/notices/horizontal-notice.php:78
msgid "Read more"
msgstr ""

#: templates/notices/thanks-for-using-main-dash.php:4
msgid "Dismiss (for %s months)"
msgstr ""

#: templates/notices/thanks-for-using-main-dash.php:6
msgid "Thank you for installing All In One WP Security & Firewall!"
msgstr ""

#: templates/notices/thanks-for-using-main-dash.php:13
msgid "Super-charge and secure your WordPress site even more with our other top plugins:"
msgstr ""

#: templates/notices/thanks-for-using-main-dash.php:17
msgid "%s makes your site fast and efficient. It cleans the database, compresses images and caches pages for ultimate speed."
msgstr ""

#: templates/notices/thanks-for-using-main-dash.php:21
msgid "%s simplifies backups and restoration. It is the world's highest ranking and most popular scheduled backup plugin, with over three million currently-active installs."
msgstr ""

#: templates/notices/thanks-for-using-main-dash.php:25
msgid "%s is a highly efficient way to manage, optimize, update and backup multiple websites from one place."
msgstr ""

#: templates/notices/thanks-for-using-main-dash.php:29
msgid "%s is a WordPress subscription extension for WooCommerce store owners."
msgstr ""

#: templates/notices/thanks-for-using-main-dash.php:33
msgid "More quality plugins"
msgstr ""

#: templates/notices/thanks-for-using-main-dash.php:33
msgid "Premium WooCommerce plugins"
msgstr ""

#: templates/partials/non-apache-feature-notice.php:9
msgid "This feature works only on the Apache server."
msgstr ""

#: templates/partials/non-apache-feature-notice.php:10
msgid "You are using the non-apache server %s, so this feature won't work on your site."
msgstr ""

#: wp-security-core.php:236
#: wp-security.php:45
msgid "This plugin requires PHP version %s."
msgstr ""

#: wp-security-core.php:237
msgid "Current site PHP version is %s."
msgstr ""

#: wp-security-core.php:238
#: wp-security.php:47
msgid "You will need to ask your web hosting company to upgrade."
msgstr ""

#: wp-security-core.php:397
msgid "Error:"
msgstr ""

#: wp-security-core.php:397
msgid "template not found"
msgstr ""

#: wp-security.php:44
msgid "All In One WP Security and Firewall plugin has been deactivated."
msgstr ""

#: wp-security.php:46
msgid "Your current PHP version is %s."
msgstr ""