[{"data":1,"prerenderedAt":137},["ShallowReactive",2],{"blog-index-en":3},[4,13,20,28,35,41,48,54,61,67,73,79,85,91,97,103,110,117,124,130],{"path":5,"title":6,"description":7,"date":8,"tags":9,"readingMinutes":12},"\u002Fblog\u002Fspreadsheet-in-spreadsheet-out","Keep a contact ID in your verification file","A simple export makes it easier to return each result to the right contact without exposing your whole CRM.","2026-07-29",[10,11],"Guides","List hygiene",1,{"path":14,"title":15,"description":16,"date":17,"tags":18,"readingMinutes":12},"\u002Fblog\u002Fthe-api-now-belongs-to-your-account","Before you connect an email verification API","Plan for unresolved checks, failed requests and changing addresses before putting verification into production.","2026-06-23",[19,10],"API",{"path":21,"title":22,"description":23,"date":24,"tags":25,"readingMinutes":12},"\u002Fblog\u002Frebuilding-the-batch-engine","Why the last few addresses can take longer","A verification job can slow down near the end because some receiving servers need more time or give no clear answer.","2026-05-22",[26,27],"Verification","Technical",{"path":29,"title":30,"description":31,"date":32,"tags":33,"readingMinutes":12},"\u002Fblog\u002Fwhat-we-store","Before you upload your contact list","Send only what the check needs, and get specific answers about retention, deletion and reuse.","2026-04-07",[34,10],"Privacy",{"path":36,"title":37,"description":38,"date":39,"tags":40,"readingMinutes":12},"\u002Fblog\u002Fwhat-we-will-not-build","Before you guess someone’s email address","A plausible naming pattern and a positive server response do not establish who will receive your message.","2026-02-16",[26],{"path":42,"title":43,"description":44,"date":45,"tags":46,"readingMinutes":12},"\u002Fblog\u002Fdeliverability-beyond-the-list","The addresses work. Why is the email going to spam?","Check authentication, recipient expectations and delivery reports before paying to clean the list again.","2025-12-05",[47],"Deliverability",{"path":49,"title":50,"description":51,"date":52,"tags":53,"readingMinutes":12},"\u002Fblog\u002Femail-list-decay","Before you email that old list","A dormant list needs a review of addresses, subscription history and whether the message still makes sense.","2025-11-04",[11,47],{"path":55,"title":56,"description":57,"date":58,"tags":59,"readingMinutes":12},"\u002Fblog\u002Femail-typos-at-signup","Ask before you fix an email typo","A useful suggestion can save a signup. An automatic correction can send mail to the wrong person.","2025-10-09",[60,11],"Signups",{"path":62,"title":63,"description":64,"date":65,"tags":66,"readingMinutes":12},"\u002Fblog\u002Fone-year-of-mailok","Before you remove everyone who never opens","Open tracking can mislead you. Review other activity before deciding a subscriber has gone quiet.","2025-09-19",[11,47],{"path":68,"title":69,"description":70,"date":71,"tags":72,"readingMinutes":12},"\u002Fblog\u002Fspam-traps","A working address can still be a spam trap","Why verification cannot certify a list as trap-free, and what to change when trap problems appear.","2025-08-26",[47],{"path":74,"title":75,"description":76,"date":77,"tags":78,"readingMinutes":12},"\u002Fblog\u002Fdisposable-email-addresses","Should you block disposable email addresses?","Decide based on what the account needs, and distinguish temporary inboxes from lasting privacy aliases.","2025-07-28",[11,60],{"path":80,"title":81,"description":82,"date":83,"tags":84,"readingMinutes":12},"\u002Fblog\u002Fsmtp-verification-explained","What an SMTP check actually tells you","A server response provides evidence about delivery, but it cannot confirm everything about a mailbox.","2025-06-18",[26,27],{"path":86,"title":87,"description":88,"date":89,"tags":90,"readingMinutes":12},"\u002Fblog\u002Fverify-email-at-signup","Check the address while the person can still fix it","Catch obvious mistakes at signup, allow for inconclusive checks, and confirm inbox access separately.","2025-05-16",[19,10],{"path":92,"title":93,"description":94,"date":95,"tags":96,"readingMinutes":12},"\u002Fblog\u002Frole-email-addresses","Keep the invoice going to accounts@","A role address describes a purpose. It does not, by itself, tell you to remove the contact.","2025-04-10",[11],{"path":98,"title":99,"description":100,"date":101,"tags":102,"readingMinutes":12},"\u002Fblog\u002Fcatch-all-email-addresses","What a catch-all result leaves unanswered","The server accepts the address. That still may not tell you whether the intended mailbox exists.","2025-03-03",[26,47],{"path":104,"title":105,"description":106,"date":107,"tags":108,"readingMinutes":109},"\u002Fblog\u002Fclean-email-list","You inherited a mailing list. Start here.","Check its source, preserve exclusions, verify the addresses, and put the results back where they will be used.","2025-01-31",[11,10],2,{"path":111,"title":112,"description":113,"date":114,"tags":115,"readingMinutes":12},"\u002Fblog\u002Femail-bounce-rate","Read the bounce reason before you clean the list","A bad address, a temporary delay and a policy block need different fixes.","2024-12-17",[47,116],"Bounces",{"path":118,"title":119,"description":120,"date":121,"tags":122,"readingMinutes":12},"\u002Fblog\u002Fwhy-unknown-is-free","Why unknown results are free","An unresolved check should remain unresolved, and MailOK does not charge for that result.","2024-11-07",[123,26],"Pricing",{"path":125,"title":126,"description":127,"date":128,"tags":129,"readingMinutes":12},"\u002Fblog\u002Femail-verification-statuses","Valid, invalid, risky, unknown: what to do next","Read verification results as evidence about an address, with the reason and check date attached.","2024-10-16",[26,10],{"path":131,"title":132,"description":133,"date":134,"tags":135,"readingMinutes":12},"\u002Fblog\u002Fmailok-launch","What you can use MailOK for","Check a contact list before a send, or check new addresses as they enter your product.","2024-09-20",[136],"Product",1790300926658]