Title: Disposable Email Blocker for WooCommerce – Block Fake and Temporary Emails at Checkout Author: stackedboost Published: 15. august, 2026 Last modified: 29. august, 2026 --- Søk i utvidelser ![](https://ps.w.org/stackedboost-email-guard/assets/banner-772x250.png?rev=3648645) ![](https://ps.w.org/stackedboost-email-guard/assets/icon-256x256.png?rev=3648621) # Disposable Email Blocker for WooCommerce – Block Fake and Temporary Emails at Checkout Av [stackedboost](https://profiles.wordpress.org/stackedboost/) [Last ned](https://downloads.wordpress.org/plugin/stackedboost-email-guard.1.3.1.zip) * [Detaljer](https://nb.wordpress.org/plugins/stackedboost-email-guard/#description) * [Omtaler](https://nb.wordpress.org/plugins/stackedboost-email-guard/#reviews) * [Installering](https://nb.wordpress.org/plugins/stackedboost-email-guard/#installation) * [Utvikling](https://nb.wordpress.org/plugins/stackedboost-email-guard/#developers) [Brukerstøtte](https://wordpress.org/support/plugin/stackedboost-email-guard/) ## Beskrivelse Bad email addresses cause failed deliveries, chargebacks, fake accounts, and support tickets. Email Guard checks the customer’s address at checkout and blocks disposable email before the order goes through, entirely on your own server, with no account required. It ships with a bundled list of over 8,200 disposable email and temporary email domains, a map of the typos people actually make, and your own block and allow lists. Every check runs locally. The plugin makes no outbound request of any kind unless you deliberately activate a Pro licence key. #### The problem, stated plainly A disposable email address is a working inbox that is designed to stop working. Services like Mailinator, Guerrilla Mail, 10 Minute Mail and several thousand others hand out an address that receives mail for a few minutes or a few hours and then discards it, usually without asking anyone to register. Some of them publish hundreds of alternate domains precisely so that blocklists cannot keep up. None of that is inherently sinister. People use throwaway email to avoid newsletters, to test something, or to sign up for a download they will never come back to. That is fine on a blog. It is a problem on a shop, because an order carries obligations that a ten-minute inbox cannot meet. Here is what actually goes wrong when a disposable email address reaches an order: * **The order confirmation bounces.** The address stops accepting mail before your transactional email arrives, or it accepts the mail and deletes it. The customer never receives an order number. * **The shipping notification never lands.** The customer has no tracking link, so they either wait or they contact you. * **The support thread starts.** You now handle by hand what your automation was supposed to handle, and you are answering somebody who cannot receive your reply. * **Your sender reputation erodes.** Repeated hard bounces to dead domains tell mailbox providers that your list is poorly maintained. That affects delivery of every other email you send, including to customers whose addresses are perfectly good. * **Discount and trial abuse gets cheap.** If a coupon is limited to one per customer, or a first-order discount exists, a supply of fresh throwaway addresses makes that limit meaningless. * **Chargeback risk rises.** An order placed behind a disposable address is harder to trace and harder to defend, because the one contact channel you have is gone by the time the dispute arrives. Not every disposable address is fraud. Most of it is friction. The point of Email Guard is to remove the friction at the one moment it is cheap to remove, which is before the order exists. #### What Email Guard does Email Guard hooks into WooCommerce checkout validation and account registration. When a shopper submits an address, the plugin runs four checks in a fixed order and either lets the order through or stops it with a message the shopper can act on. **1. Your allow list wins over everything.** If the domain is on your allow list, the address passes immediately and no further check runs. This is deliberate and it is checked first, before anything else, including the bundled list of 8,200 domains. At that size a false positive stops being hypothetical, and a shop owner needs a way to overrule the plugin that does not mean switching protection off for everybody. If a real customer is ever refused, you add their domain and they are through, permanently. **2. Your own blocklist.** Domains you have added yourself are refused next. This is for the addresses that are not disposable but that you do not want ordering: a competitor, a domain that has produced repeated fraud, a free provider your business does not serve. It is your list, it is checked on every order, and it takes precedence over the typo and disposable checks below. **3. Likely typos, with a correction offered.** If the domain looks like a near-certain mistake, the shopper is shown the corrected address rather than a flat refusal. «Did you mean bob@gmail.com?» recovers a sale that a plain error message loses. The bundled typo map covers 34 of the mistakes people make most often on the large providers. It handles the two distinct kinds. Misspelled names: gmial.com, gnail.com, gamil.com, hotmial.com, hotmali.com, yhaoo. com, outlok.com. And truncated or fumbled endings, which are just as common and easier to miss: gmail.con, gmail.co, yahoo.con, outlook.co, icloud.con, aol.co, live.con, protonmail.con. The providers covered are Gmail, Hotmail, Yahoo, Outlook, iCloud, AOL, Live and Proton Mail, which between them account for the overwhelming majority of consumer addresses that reach a shop. This check runs **before** the disposable check, which is not an accident. Several well-known typosquats are on the disposable list, because somebody registered them specifically to catch mistyped mail. Checking disposable first told a shopper who fat-fingered «gmail» that disposable addresses are not accepted. True of the domain, and completely useless to the person trying to buy something. The order is stopped either way. This way they can fix it. **4. The bundled disposable email list.** Finally, the address is checked against over 8,200 known disposable email and temporary email domains. The list is a file inside the plugin, not a service call, so it works whether or not your server can reach the internet, and no customer address is ever transmitted anywhere. #### Subdomain matching, and why it matters Throwaway providers hand out addresses on subdomains constantly. A service listed as example.com will happily issue you an address at mail.example.com, inbox.example. com or a random string in front of it. A blocklist that only compares the whole domain string misses every one of those. Email Guard walks the labels of the address domain from the left and stops when two labels remain. An address at deep.sub.mailinator.com is tested as deep.sub.mailinator. com, then sub.mailinator.com, then mailinator.com, and is refused on the last one. The same walk applies to your own blocklist, so adding competitor.com also covers shop.competitor.com without you listing it. Over-stripping is safe here. A candidate only has an effect if it is actually present in one of the lists, and real public suffixes are not. Testing «co.uk» against the list costs one array lookup and cannot produce a false positive, because «co.uk» is not a disposable domain and nobody would put it on a blocklist. #### Where the checks run Email Guard validates in three places, which between them cover how WooCommerce actually takes orders: * **Classic checkout** (the shortcode checkout), through `woocommerce_after_checkout_validation`. A blocked address surfaces as a checkout notice and the order is not created. * **Block checkout** (the Cart and Checkout blocks, via the Store API). A blocked address stops the order when «Place order» is pressed and the message appears in the block’s error state. Many email plugins only ever hooked the classic checkout and silently do nothing on a block-based store. This one handles both. * **Account registration**, through `woocommerce_registration_errors`, which covers both the My Account registration form and the create-an-account option during checkout. If WooCommerce is not active, the plugin does nothing to your site except show an admin notice explaining that it needs WooCommerce. It does not touch WordPress core registration, the comment form, or any contact form. #### What this plugin deliberately does not do Being specific about scope is more useful than claiming everything. * **It is WooCommerce-only.** It protects checkout and WooCommerce account registration. It does not filter WordPress core registration, comments, or contact form submissions. If you want to block disposable email on a site that has no shop, this is the wrong plugin. * **It does not verify that a mailbox exists.** Checking whether a specific inbox is real requires talking to the receiving mail server at the moment of the order. The free version makes no outbound requests, so it cannot do that, and it does not claim to. Domain-level checking catches disposable providers and typos, which is the overwhelming majority of what goes wrong. * **It does not score orders for fraud.** It makes a yes or no decision on an address at checkout. It does not analyse payment method, address mismatch, order velocity or device. * **It does not send anything anywhere.** No telemetry, no analytics, no phone- home licence check on the free version. This is a promise about the code, and it is easy to verify: search the plugin directory for `wp_remote_` and you will find outbound calls only in the Pro licence activation path, which runs only if you enter a key. #### Privacy, and what is stored The plugin’s whole pitch is that it makes no outbound requests and keeps no customer data, so it is worth being exact about the small amount it does record. **What is stored:** counters in your site’s own options table. How many blocks fired, split by reason. Which **domains** were refused and how many times. Which typo corrections were offered. A daily count for the last 30 days so the dashboard can draw a line. That is it. **What is not stored:** no email addresses. The local part of the address is discarded before anything is written. No names, no order IDs, no IP addresses, no user agents. A domain is not personal data: «mailinator.com» identifies a mail provider, not a person. **Where it is stored:** the `sbeg_stats` option on your own site, written with autoload set to false so it is not loaded on front-end requests. It is never transmitted. **When it is written:** only when a block actually fires, which on a typical shop is a few times a week rather than once per checkout. Nothing is written on a normal order. **Growth is capped.** The daily series keeps 30 days. The domain and typo tables keep the 12 most frequent rows. A shop hit by many distinct throwaway domains cannot grow the option without bound. **On uninstall**, the plugin deletes `sbeg_settings`, `sbeg_stats`, `sbeg_review_dismissed` and `sbeg_license`. Removing the licence record does not release the activation slot on your account; that stays with you to manage. #### Performance The bundled domain list is a plain newline-delimited text file of about 116 KB. It is read on the first check that actually needs it and not before. That laziness is the point. The plugin is loaded on requests that never validate an address, and holding 8,201 domains permanently in memory to answer a question that only arises at checkout is waste. Shipped as a PHP array it would have been roughly a quarter of a megabyte held in opcache on every single request. Read from a file on demand it costs nothing until it is needed, and once per request after that. Lookups are array key hits, not string scanning, so a single check is a handful of hash lookups regardless of whether the list holds 50 domains or 8,201. #### The dashboard Under **WooCommerce > Email Guard** you get a screen that answers one question: is this thing doing anything? * Total addresses refused, split into disposable, typo and your own blocklist. * A 30-day line so you can see whether it is a steady trickle or a spike. * The domains that were refused most often, so you can see who is actually hitting you. * The typo corrections that were offered, and to what. * A live tester: type any address and see exactly what checkout would do with it. It runs the same validator the checkout uses and does not touch your counters. * An example view, if you have no data yet, that shows what the screen looks like on an active shop. It is clearly labelled, it is generated on the spot, and nothing is saved to your database. #### Email Guard Pro (optional) Pro is not a bigger list. The free list is not limited in any way and Pro does not extend it. Pro is the set of checks that a bundled file cannot perform at all, because they need a live lookup at the moment the order arrives: * **DNS and MX deep scan**, to catch domains that resolve but cannot receive mail at all. A bundled list cannot know this; it changes. * **Post-order risk scoring and automatic order tagging**, so risky orders are flagged in your order list before you pick and ship. * **Instant alerts** when a risky order lands. * **A hosted risk dashboard** across your orders. Pro is a separate add-on from Stackedboost and is not required to use the free version. Everything listed above under the free version keeps working whether or not you ever buy it, and keeps working if a Pro licence lapses. Available at https://stackedboost.com/woocommerce/stackedboost-email-guard/ #### Credits The bundled domain list is derived from the disposable-email-domains project, dedicated to the public domain under CC0 1.0. Attribution is not required by that licence; it is given because the work deserves it. ## Skjermbilder [⌊A disposable address refused at checkout, before the order is created.⌉⌊A disposable address refused at checkout, before the order is created.⌉[ A disposable address refused at checkout, before the order is created. [⌊A likely typo caught, with the correct domain suggested.⌉⌊A likely typo caught, with the correct domain suggested.⌉[ A likely typo caught, with the correct domain suggested. [⌊The Email Guard dashboard: what was blocked, what was corrected, and your settings.⌉⌊ The Email Guard dashboard: what was blocked, what was corrected, and your settings .⌉[ The Email Guard dashboard: what was blocked, what was corrected, and your settings. ## Installasjon 1. Upload the plugin to `/wp-content/plugins/` or install it from the Plugins screen. 2. Activate it through the **Plugins** screen. 3. Make sure WooCommerce is active. 4. Go to **WooCommerce > Email Guard** to configure blocking, typo suggestions, and your own block and allow lists. That is the whole setup for the free version: there is no account to create and nothing to connect. Protection is on from the moment you activate, with sensible defaults, and you do not have to configure anything for it to start working. #### Recommended first five minutes 1. Open **WooCommerce > Email Guard**. 2. Use the tester. Type `test@mailinator.com` and confirm it is refused. Type your own address and confirm it passes. This tells you the plugin is live and doing what you expect, without waiting for a real order. 3. Type `test@gmial.com` to see what a typo correction looks like to a shopper. 4. If you have domains you already know you want to refuse, paste them into the custom blocklist, one per line. 5. Leave the allow list empty for now. Add to it only if a real customer is ever refused. #### If you bought Pro Paste your licence key into the **Email Guard Pro licence** box on the same settings screen and press **Activate licence**. One licence covers one site; you can move it to another site from your account at any time. ## Ofte stilte spørsmål ### Does this send customer data anywhere? No. The free version performs all checks locally on your own server using bundled lists. Nothing is sent to any external service. There is no telemetry, no analytics and no licence check in the free version. The only outbound request the plugin can make is to the Stackedboost API, and only if you deliberately enter a Pro licence key to activate it. ### Does it require WooCommerce? Yes. Email Guard protects the WooCommerce checkout and account registration. It does not touch WordPress core registration or comments, so if you want to block disposable email on a site without a shop, this is not the plugin for it. ### Does it work with the new block-based checkout? Yes. Email Guard validates both the classic (shortcode) checkout and the newer Cart/ Checkout blocks (Store API). On the block checkout, a blocked email stops the order when «Place order» is clicked and the message appears in the block’s own error state. This is worth checking on any email plugin you evaluate. A plugin that only hooks the classic checkout does nothing at all on a block-based store, and it fails silently, which is the worst way to fail. ### Will it block real customers? The bundled list contains disposable email and temporary email providers only, and the typo map covers near-certain mistakes. If a real customer is ever refused anyway, add their domain to the allow list on the settings screen: it overrules everything, including the bundled list, so you never have to switch protection off to let one person through. ### A real customer was blocked. What do I do? Add their domain to «Always allow these domains» on the settings screen. The allow list is checked first, before every other rule, so the customer is through immediately and permanently. If you want to understand why it happened first, paste the address into the tester on the same screen. It will tell you which of the four checks refused it, so you know whether it was the bundled list, your own blocklist or the typo map. ### Does it catch subdomains? Yes. An address at mail.example.com is refused if example.com is on any list, which is how throwaway email providers usually hand out addresses. The same applies to your custom blocklist: adding competitor.com also covers orders.competitor.com. ### Can I use it to block a specific company or competitor? Yes. Put their domain in the custom blocklist, one per line. It is checked on every order, it covers their subdomains automatically, and it takes precedence over everything except your allow list. ### What is the difference between disposable, temporary and throwaway email? In practice they are the same thing under different names, and this plugin treats them identically. A disposable email address, a temporary email address and a throwaway email address all describe an inbox that is meant to be abandoned: usually free, usually requiring no registration, and usually dead within minutes or hours. You will also see «temp mail», which is the same idea and is the brand name of several of the larger providers. ### What about catch-all domains and plus addressing? Neither is blocked, and neither should be. A catch-all domain accepts mail to any address at that domain. Plenty of legitimate small businesses run one. Blocking catch-alls would refuse real customers in volume. Plus addressing (`name+shop@gmail.com`) is a normal, supported feature of the major providers, used by people who want to filter their own mail. It is not disposable, and refusing it annoys exactly the sort of organised customer you want. ### How often is the domain list updated? The list is bundled with the plugin, so it updates when the plugin updates. It went from about 50 domains to over 8,200 in version 1.2.0. A bundled list is a deliberate trade. It never phones home, never leaks a customer address, and works if your server has no outbound access, but it is a snapshot rather than a live feed. No blocklist is complete, and anyone who says otherwise is selling something: disposable providers register new domains constantly. If the tail of newly registered domains matters to your shop, that is what the DNS and MX checks in Pro are for. ### How does this compare to other ways of validating email? Four common approaches, solving different problems. **Regular expression format checks.** Confirms an address looks like an address. WooCommerce already does this and it catches nothing that matters: `x@mailinator. com` is perfectly well formed. **A bundled domain list, which is this plugin.** Fast, private, free, works offline, no per-check cost, catches the providers used at volume. The trade is that it is a snapshot. **Live DNS and MX lookups.** Asks whether the domain can receive mail at all. Catches dead and misconfigured domains no list can know about, at the cost of a network round trip. This is what Pro adds. **Third-party validation APIs.** The most thorough and the most expensive in every sense: per-check fees, a network dependency inside checkout, and you are sending customer addresses to another company. That privacy decision should be yours, not a default someone picked for you. Neither this plugin nor Pro is a fraud system. A shop with real fraud exposure needs more than email validation. ### Should I block gmail.com and other free providers? No, and this plugin will never do it for you. You will see this advised for B2B shops, on the theory that a real business has its own domain. An enormous number of legitimate sole traders, contractors and small businesses buy using a free address, and plenty of large ones do too. Refusing free providers does not filter fraud. It filters customers, silently, at the exact moment they were about to pay you. If your business genuinely cannot serve consumer addresses, the custom blocklist will let you do it. That is your call to make deliberately, not a default. ### What should the dashboard numbers make me do? **A steady trickle of blocks.** The normal, healthy state. Nothing to act on. **One domain dominating.** You are being probed rather than casually shopped. Check whether it lines up with a discount code being live. **A spike from many domains at once.** Somebody working through a list, usually against a first-order discount. The plugin is already refusing them, so the decision is about the offer, not the plugin. **Typo corrections climbing.** Often the most valuable number on the screen. Every typo caught is an order that would otherwise have completed with an address that silently bounces. **Zero blocks after several weeks.** Not a fault. Your traffic is clean. Confirm with the tester, then stop thinking about it. ### What does each setting do? Everything is on one screen at **WooCommerce > Email Guard**. **Block risky emails at checkout.** The master switch. Off means every check is skipped and nothing is refused or recorded. **Suggest corrections for typos.** On, a likely typo stops checkout and shows the corrected address. Off, typos are ignored and only disposable domains and your own blocklist are enforced. **Custom blocked domains.** One per line, or comma separated. Pasting a whole address works; the plugin takes the part after the @. Subdomains are covered automatically. **Always allow these domains.** Same format. Checked before every other rule, including the bundled list. Your override and your safety valve. **The tester.** Type any address and see the verdict and the reason. It runs the same code path as checkout and does not touch your counters. ### Nothing is being blocked. Is it broken? Probably not. Check that «Block risky emails at checkout» is on, then use the tester with `test@mailinator.com`. If the tester refuses it, the plugin is working and your traffic is simply clean. ### The block checkout is not stopping orders Confirm it is the WooCommerce Cart/Checkout block and not a third-party checkout that bypasses the Store API. Email Guard validates the classic checkout and the Store API. A checkout that goes around both cannot be validated by any plugin hooking WooCommerce. ### I cannot find the settings page It sits under **WooCommerce** when WooCommerce is active, and under **Settings** when it is not. There is also a Settings link on the plugin’s own row in the Plugins screen. ### The counts look wrong, or stopped moving Counters are written only when a block actually fires, so a quiet week writes nothing. The daily series keeps 30 days and older days fall off by design. ### Does it slow down my checkout? No measurable amount. The checks are hash lookups against an in-memory array, and the domain list is only read on requests that actually validate an address. Requests that never reach checkout never pay for it. ### Does it work without WooCommerce Blocks / on older WooCommerce? Yes. The Store API integration is resolved at runtime and the plugin falls back cleanly if the block checkout classes are not present, so it works on stores still using the classic checkout only. ### Can I turn off the typo suggestions but keep disposable blocking? Yes. They are separate switches on the settings screen. With typo suggestions off, a mistyped address no longer stops checkout, and only disposable domains and your own blocklist are enforced. ### What exactly does the shopper see? For a disposable address: «Disposable email addresses are not accepted. Please use a permanent email.» For a likely typo: «Did you mean bob@gmail.com? Please check your email address.» For a domain on your own blocklist: «This email domain is not allowed for orders.» All three are translatable through the plugin’s text domain. ### Is it translation ready? Yes. All merchant-facing and shopper-facing strings use the `stackedboost-email- guard` text domain and the plugin ships with no hard-coded English in its output. Translations submitted through translate.wordpress.org are picked up automatically. ### Does it store customer email addresses? No. The local part of the address is discarded before anything is recorded. The counters hold domains only, plus how many times each was refused. See the privacy section above for the full list of what is and is not stored. ### Is it GDPR compliant? The free version stores no personal data about your customers, makes no outbound request, and sets no cookies, so it does not add a processor to your stack or give you anything new to disclose. Domain-level counters on your own server are not personal data. That is a description of what the plugin does, not legal advice. Your own obligations depend on everything else your site does. ### What happens to my data if I uninstall? Everything the plugin created is removed: your settings, the local counters, the review-prompt flag and the licence record. Nothing is left behind in your database. ### Does the free version phone home or check a licence? No. The free version never contacts any server: there is no licence check, no telemetry, and no upsell nag beyond the settings screen. The plugin only makes an outbound request if you deliberately activate a Pro licence key, and then only to the Stackedboost API. ### What does Pro add? Checks that cannot be done from a bundled file: a live DNS and MX lookup to see whether the domain can actually receive mail, risk scoring on the finished order, order tagging and alerts. The disposable blocking in the free version is not limited in any way, and Pro does not make it bigger. Pro is optional and sold separately at https://stackedboost.com/woocommerce/stackedboost- email-guard/. ### What happens if my Pro licence expires? The site quietly returns to the free version: local blocking, typo suggestions and your custom blocklist keep working exactly as before. Nothing is disabled and no data is removed. ### Are there hooks or filters for developers? Not yet. The plugin exposes no public actions or filters at this time, and it would be dishonest to list any it does not have. If you need a specific hook, say to add domains programmatically or to change a message, open a thread on the support forum and describe the use case. That is the fastest way to get one added. ### Why was my order blocked when the address looked fine? Use the tester on the settings screen. Paste the address and it will tell you which check refused it and why, using the same code path the checkout uses. From there it is either a domain you want to allow, in which case add it to the allow list, or a domain that is genuinely on the disposable list. ### Does it work on WordPress Multisite? Yes. Each site keeps its own settings, lists and counters. Network activation works and every site is configured independently. ### Will it work if my host blocks outbound connections? Yes, completely. That is one of the reasons the domain list is bundled rather than fetched. The free version never needs outbound access for any part of its job. Locked- down hosting, a firewalled staging environment or a server with no route to the internet all work identically. ### Does it need cron, or a background job? No. Every check happens inline during the request that submits the address. There is no scheduled task, no queue and no background processing to go wrong. ### Does it conflict with other email or anti-spam plugins? It should not. It adds validation errors through WooCommerce’s own validation hooks rather than replacing or short-circuiting anything, so other plugins hooking the same points continue to run. If two plugins both refuse an address, the shopper sees both messages. ### Can I see what would have been blocked before I turn it on? Not as a passive monitoring mode, no. What you can do is use the tester to check any address you are curious about, including ones from past orders, and see exactly what checkout would have done with it. That gives you the same answer for the addresses you actually care about, without changing anything. ### How do I report a domain that should be blocked, or one that should not? Open a thread on the support forum with the domain. False positives are treated as the higher priority of the two, because a wrongly refused address costs a real order. ### I run a B2B store and some clients use unusual domains. Is this safe? Yes, with one habit: keep the allow list as your safety valve. Corporate domains are not on disposable lists, so in practice B2B stores see very few false positives. If one does happen, the allow list resolves it in seconds and permanently. ## Vurderinger Det er ingen omtaler av denne utvidelsen. ## Bidragsytere og utviklere «Disposable Email Blocker for WooCommerce – Block Fake and Temporary Emails at Checkout» er programvare med åpen kildekode. Følgende personer har bidratt til denne utvidelsen: Bidragsytere * [ stackedboost ](https://profiles.wordpress.org/stackedboost/) [Oversett «Disposable Email Blocker for WooCommerce – Block Fake and Temporary Emails at Checkout» til ditt språk.](https://translate.wordpress.org/projects/wp-plugins/stackedboost-email-guard) ### Interessert i utvikling? [Bla gjennom koden](https://plugins.trac.wordpress.org/browser/stackedboost-email-guard/), sjekk ut [SVN-repositoriet](https://plugins.svn.wordpress.org/stackedboost-email-guard/), eller abonner på [utviklingsloggen](https://plugins.trac.wordpress.org/log/stackedboost-email-guard/) med [RSS](https://plugins.trac.wordpress.org/log/stackedboost-email-guard/?limit=100&mode=stop_on_copy&format=rss). ## Endringslogg #### 1.3.1 * Renames the plugin so the directory listing leads with what it does rather than with the author name. No code change. #### 1.3.0 * Adds the `sbeg_check_result` filter, so a separately sold add-on can run a live check on an address the bundled list has already cleared. Nothing in this plugin listens to it, and with no add-on installed the plugin still makes no outbound request of any kind. * No change to what the free version blocks. The bundled list, the typo map and your own lists are unchanged and remain uncapped. #### 1.2.5 * Tested up to WordPress 7.1. #### 1.2.4 * The Pro card now shows the price, and leads with how many bad addresses this store has actually refused rather than a list of technical features. * The licence key field moved behind «Already bought it?», since it is only useful to people who have already paid. * No change to any check, setting or stored data. #### 1.2.3 * Fixes the Description being truncated on WordPress.org. It ran to 3,241 words against a 2,500 word limit, so everything from the comparison section onward, including the Pro section and the credits, was silently cut from the public page. The reference material (settings, dashboard, troubleshooting, comparison) moved into the FAQ, which is where it belonged anyway. #### 1.2.2 * Documentation only, no code changes. The readme now explains what disposable email actually costs a shop, what the plugin checks and in what order, exactly what is and is not stored, and where the plugin’s scope ends. Adds a substantially larger FAQ covering catch-all domains, plus addressing, GDPR, block checkout support and what a shopper sees. #### 1.2.1 * Wording only, no code changes. The listing described what the plugin does using« temp-mail» and «throwaway providers», which is how a developer writes it, not how a shop owner searches for it. It now says disposable email, temporary email and throwaway email in the places those are the accurate words. #### 1.2.0 * The bundled disposable list grows from about 50 domains to over 8,200, from the public-domain disposable-email-domains project. Still bundled, still no outbound request. * Subdomains are now caught. An address at mail.example.com is refused when example. com is listed, which is how most throwaway providers hand out addresses. * New: an allow list that overrules everything, including the bundled list, so a wrongly refused customer no longer means switching protection off. * Mistyped addresses now offer the correction even when the mistyped domain is itself on the disposable list. Several well-known typosquats are, and telling a shopper their address is disposable gave them no way to fix it. * The list loads only when an address actually needs checking, so requests that never reach checkout do not pay for it. #### 1.1.2 * Renamed in the directory to say what the plugin does, so it can be found by people searching for a disposable-email blocker. Nothing in the plugin changed. #### 1.1.1 * Added a Settings link to the plugins list, so the dashboard is easier to find. * Added a Support link, and a one-time pointer after activation. * No change to how email checking works. #### 1.1.0 * New: a dashboard at WooCommerce > Email Guard showing how many risky addresses were refused, which typos were corrected, and which domains were blocked. * Counts are kept on your own site and never sent anywhere. Domain names only, no customer address is stored. * New: test any address from the settings screen and see exactly what checkout would do. Test checks do not affect your counts. * New: preview the dashboard with example figures before your own activity builds up. The example is never saved. * Redesigned the settings screen around that information. #### 1.0.1 * The «Buy a licence» button now opens the product page instead of the checkout directly, so you can read what Pro adds before paying. * Added the plugin’s product page to its header. * No changes to how email checking works. #### 1.0.0 * Initial release: local checkout + registration email validation (disposable, typo, custom blocklist). ## Meta * Versjon **1.3.1** * Sist oppdatert **3 dager siden** * Aktive installasjoner **Færre enn 10** * WordPress-versjon ** 6.0 eller nyere ** * Testet opp til **7.1** * PHP-versjon ** 7.4 eller nyere ** * Språk * [English (US)](https://wordpress.org/plugins/stackedboost-email-guard/) * Stikkord * [disposable email](https://nb.wordpress.org/plugins/tags/disposable-email/)[email validation](https://nb.wordpress.org/plugins/tags/email-validation/) [fake email](https://nb.wordpress.org/plugins/tags/fake-email/)[temporary email](https://nb.wordpress.org/plugins/tags/temporary-email/) [woocommerce](https://nb.wordpress.org/plugins/tags/woocommerce/) * [Avansert visning](https://nb.wordpress.org/plugins/stackedboost-email-guard/advanced/) ## Vurderinger No reviews have been submitted yet. [Din omtale](https://wordpress.org/support/plugin/stackedboost-email-guard/reviews/#new-post) [Se alle omtalene](https://wordpress.org/support/plugin/stackedboost-email-guard/reviews/) ## Bidragsytere * [ stackedboost ](https://profiles.wordpress.org/stackedboost/) ## Brukerstøtte Har du noe å si? Trenger du hjelp? [Vis brukerstøtteforumet](https://wordpress.org/support/plugin/stackedboost-email-guard/)