467 Matching Annotations
  1. Last 7 days
    1. nted email actu

      And the last noise you see or get in your certificates because there's less emails that don't exist. They are also fake opening and might be skewering your decision-making.

    2. ere consent gets misunderstood.

      We need to make it clear. The email marketing software providers are unable to give a real sperm rate. The largest portion of the list is un included in that spam rate we need to make that clear.

    3. s the bil

      I want a good time to explain to people how different even marketing tools charge people with some of them will charge them even if the contact is unsubscribe and some will even allow you to add an email in the suppression list, but will remain active in the main list and some, if not all of them will charge you for duplicate contacts or multiple lists and then we also should explain that if people are in multiple lists and subscribe the subscribe from the list they don't subscribe from the account, so therefore people might have the impression they're unsubscribing and then they get an email from another list that they're in on your end and they get angry and complain and then you have no idea because of the complaints and spam rates aren't given yada yada

    4. ly way to know an address is real is to read the address itself, and that is exactly what we do. Almanac: catch-all / a

      this is a bit too on the nose? we ned to be ore smooth or add things os it doensT' sound lieka sles pitch lol

    5. n email list is not a fixed thing you build once. It is alive, and a slice of it goes bad every single year.

      we can show calaultaor here no? or a cool version of it? ad some the other way aroudn right? like when trackign pizel doesnt ping or downoad or open

    6. Since 2021, Apple's mail app quietly loads every image before a human even looks, which fakes an open.

      we keep saing apple 2021, but like gmail has been prefetching or micsosft uderfetching fro years its ot jsut apple they jsut made it public

    7. ver says yes, we got it, and then nobody ever sees it. Your email tool counts that as delivered. It looks perfect. And it reached no one. On a business list, this can

      we can say like you deliverablity tab isn't a deliverbaility tab, its jstu a delivery tba that shows you thigns that are miinsterpratred weirdly

      and then google postmaster dns yahoo sender heub that sreal , toosl liek emailconsul show real deliverbaility and sender reptuation adn everm then ther are limitaitons.

    8. sy to miss is that it does not happen all at once. It happens a little at a time, quietly, while the number on your dashboard only ever goes up. So the real question is not wh

      at some poitn shoudl probably say how logn it take osn average for a list to be more stale aan alive

    9. The number one thing to manage in email is not your subject line. It is your list.

      the number one thing or the first thing to thinkg about or something )jsut so we don't compete with kennedy's message) we have to be more smooth

    10. ou have 100,000 contacts. You are probably emailing far fewer

      the on screen ... feel a lot of talkign coudl be translated as a animation in the background that goes with what someone says no? i mean i dont' knwo how we time it with nakimbe sayign things but jow cool owuld it be to animate things?

    1. E · Which oneRME-9A question across the banner with three example addresses beneath it and no answer given.

      these are prtty cool, but technically it would be all three? xD might need to rethink what we say in the regualr banner.

    2. Your results

      REVIEW: Banner picks: company page and holiday (RME-9 · RME-10) Reviewer: YT · 9/22/2026, 4:40:14 PM Decided 4 of 6

      ▸ Company page banner [pick one] · C · Both are true [RME-9] · D · One list, three answers [RME-9] · E · Which one [RME-9] · H · One list, three answers (with addresses) [RME-9] (no choice yet)

      ▸ Halloween 2026 [pick one] · A · The line [RME-10] · C · Trick or treat [RME-10] · D · Haunted inbox [RME-10] (no choice yet)

      ▸ Q4 holiday banners [keep or cut] KEEP Black Friday · Nov 27 [RME-10] KEEP Cyber Monday · Nov 30 [RME-10] KEEP Christmas · Dec 25 [RME-10] note: but fix design, on my end the list is breoken the x and chekcbox too?

      KEEP New Year's Eve · Dec 31 [RME-10]

      OVERALL: (none)

    3. Q4 holiday bannersKeep or cutOne per date, with no competition, so just keep the ones worth publishing and cut the rest.Cyber Monday · Nov 30RME-10Amber accent bar: Friday was the send, today is the bounce report.1128 × 191 px · true sizeKEEPCUT

      don't put liikne on the left, add as rule in branding guidelies, this is the third one so far. bvubt the text is gerat

    4. D · Haunted inboxRME-10Dark banner, “Something on your list is haunting your sender reputation,” three inbox rows at the right with the middle one flagged amber.

      this is the one i choose. lets make sure (maybe just in quiz it is broken?) but the label icons next to the three email is missing. also we don'T use thinck line bars on boxes, shows as ai too much. so remove the yello line, just put the labelicon in the cicrlce next yo the email

    5. A · The lineRME-10Teal banner, the serif line “Some of your subscribers are already ghosts” set clear of the logo, a small faint ghost at the right.

      I like this but I would but the ghost a different color so we can see it a bit better?

    6. C · Both are trueRME-9

      the valid icon is wrong also it isn'T valid it is to keep. also we have to decide the label icons n also to monitor is missing, even though i understand that the banner is talking abotu an email and what we would say, but it might make people think it is the only status and labels we give. maybe e need to rethink it.

      also we need to decide label icon vs text next to it, how much taller/bigger it can be vs text. the icon should be bigger in heght than the text nto same, so we can see it. we also have dark mode of the icon i believe with a fine white line around? we shoudl use that when background isn't white or beige or an o the other light colors

    1. the Almanac-to-video pipeline Present this process

      I would really like to find the past one in my download folders. It's gonna be a folder with a video on it. That video should be able to give you the date to help you find how we generate them the scripts how we then went to create the voice and the captions and then how it works for the terminal, etc., and one of the things were really gonna need help with for V or maybe she needs to find somebody is how we're gonna do the background music and things like that and I don't mind paying when we've done all the videos paying for a month or two a little bit higher to clone my voice and my face maybe and then my face in the corner, which we then decide my face always there is it just my voice or is it a man's voice or is it a couple of different voices based what we're talking about maybe that's the ship shaped characters you know I don't know. Maybe it's a question for V to decide there's a lot of these questions and thoughts that we could present to her so that she can see well and make a good decision for us once we've kind of confirmed all of this obviously.

    2. The first one we run

      Did you find the process we use in order to create the first one? What is email because the script and the video came out really well we did do other video things and I'd like to add and edit maybe even though what his email not the content but like the video maybe just because who might come up with better smarter animations that are grounded and we also need to process right to keep these somewhere because some things like if you're talking about SPF and how it works, where we designed an animated header we might reuse it or we might reuse the base of it in order to make it different and change it, but at least we don't have to re-create things always from scratch, which then uses less tokens and also ensure that everything is correctly branded. This is also a great time to double check that her branding isn't getting confused or you know this organized because we have different projects and then are adding random things we shouldn't be adding.

    3. s the Almanac playlists, the cuts as the social track, across YouTube, TikTok and Instagram.

      Even if we might not be publishing, something somewhere the descriptions and whatever should be done on a social media level just because they have different character limit so you can put your L some of them we have to be reminded to add it as like a sticker like on it Instagram stories we have to do it manually so we need all that information organized somewhere in a database because this is a lot of stuff to manage and a lot of steps and we're not gonna be doing a continuously we're gonna start and we're gonna stop everything tracked correctly and we need to learn things as we go so that there's less corrections and back-and-forth

    4. nd social

      Just making sure we're on the same page it doesn't have to be an actual exact card like we take a long video. We just cut it into like trim it. It can be a rewrite in order for it to be Pierre in a shorter sentence so that it works for social media in places where videos can't be a minute a minute and a half two minutes plus

    5. nd screen it

      How about we do it in order and then also we have a page connect here or like whatever drop down I don't know somewhere where we can see which questions we have actually done what part like the square versus the video versus posting it versus the M4 versus the cards versus you know every single step EV all the reviews like everything on the table and if at some point, some questions or combined in the same video for whatever reason that becomes a combined role of videos instead of each line being its own QA/video role in this table page to track process

    6. confir

      We will create the first version of the storyboard, but we can add her own ideas when she comes up with better ideas to have animations that are gonna keep people listening you know more of the page or things are gonna be used, but the points to create a storyboard where we talk about normal email things, but find a way to visualize that or explain things by creating mind animation just putting text making a list of examples means whatever makes sense using obviously the information from the email Monarch

    7. ueued to post.

      vy is going to be the one who confirms the resized didn't break or things have moved and will also be the one scheduling and preparing the post to put online whether it's for the LinkedIn page my personal page, her personal page, Diego, Bruno, or cat's personal page on LinkedIn or TikTok or YouTube shorts or YouTube long format which we're gonna be recruiting the email as a pla then the audio version of that with the video or the exact same but for Spotify and then confirming the descriptions, the PDFs or generating tickets saying hey, in order to post this, we have a description, but I would like to have the description with a lead magnet. The lead magnet she can choose from could be the ones that are still in drafts that I haven't finished which then organizing and pushes me to create them, which is kind of good because it fixes and opens new funnel options on the email monarch pages. It's a task I need to do so might as well create the lead magnets from the ones we already have drafted and kind of almost done, but I actually have to build them using our template system or maybe she has another idea or you help her come up with another idea that would be great for that particular video which would then also I guess be a good thing to add as another option for lead magnet on the actual email almanac page or use it for a social media in general on its own specific learning page right

    8. From one Almanac answer to every cut

      this is correct title font style with one font dark green and then italics and bolder in teal. can we update on preview on all pages, and then push on prodafter testing othign broke? cause i eealized our headers lost this design style accross the board, and alos different font sizes, etc on pages or even between prod and and preview. we can create as new ticket for TT chat, and then TT can manage and push the pill when time to do it

    1. How big is your list?Roughly how many contacts you store.Under 5,0005,000 to 25,00025,000 to 100,000

      these options should be different based ont he esp and how things are paid /scale f paid, or plans etc. we havethis info

  2. Sep 2026
    1. How It WorksPricingLearnEmail AlmanacQ&A knowledge hubRisk Quiz2-minute deliverability checkSelf-AuditScore your email programToolsAuth & DNSDMARC XML AnalyzerDMARC Record GeneratorDMARC CheckerSPF Record CheckerBlacklist CheckerMTA-STS CheckerAnalysisEmail Header AnalyzerEmail Source AnalyzerContent & DesignSubject Line TesterEmail Signature AnalyzerEmail Accessibility CheckerInternalComponents referenceAll Free Tools →AboutSOS HotlineClean Your ListHow It WorksPricingEmail AlmanacRisk QuizSelf-AuditAll Free Tools →AboutSOS HotlinePartnerClean Your List5 minute read

      menu is wron color, also too many options lets leave the sign up option get strted and one more link like pricing? how it works?

    2. CompanyAboutPartnerDirectorySecurityContactahoy@reviewmyemails.com

      footer is not made for landing page lead magnet. shuld be thinner footer wtih logo and tradm eark plu sa create account no? then the 2026, tc under the line?

  3. Aug 2026
    1. And not every bad address bounces. Plenty are quietly accepted, then ignored, which is why a clean-looking bounce rate tells you so little

      perfect.

      lets not make it look visually similar to the bo under it.

      lets make those two statements sisually better looking

    2. Step 1 of 6

      the open now, should be more still open, closed, if a human has reviewed and chosen 10, but they can still click to get promo in exchange to the waitlist signup form/process thigns

    3. Step 4 of 6

      this too can be mulit select, bold , italics, rotate, wtb so peopel can skim options easily. ther has to be research on this we ca mplement, some pshycologial trick or somethign to ge tmore peopel to answer btter

    4. In one recent clean, 46% of a 318,000 address list should not have been sent to. The owner had no idea

      in the section we should state not all invalid emails bounce. replace with the 26% stat or wtv and the url where it was from

    Annotators

    1. (no dialogue — stares at empty table, then camera, alarmed) AWAITING your verdict

      This is completely wrong the table thing was supposed to happen during one of the tanks but we can just forget it

    Annotators

    1. OK but listen. I sent ONE question. One. I got back a detailed report, and a plan of what to d

      how about this is the blocklist person who keeps getting cut off?, but somhow his gossip is in the testimonial reivew.

      The funny part can also be that the one question was about how to get off the blacklist right and go to record step-by-step what to do everything done and they got like a warm-up and got listed and then the really laying other than like maybe what did they do to you it's that's not even what you do the clean emails addresses or whatever this was just free help. Because they wanna help? and so quick ...

      and maybe there is like a shadow that always kind of appears and thats why she is whispering and looking around or at her nails when her attiute has t ocome out more than the fear.

      kind of the liek the funny fear jokes from the language app, where the owl comes to yourw indow at night or wtv, but different version of that?

      so we merge the whisper person with the person we cut off and merge them into just t ehsos weird omg why so nice. whats the catch. which is true, everyobe is like apprehensi eot get on a call and then they are liek holy shit best callive had in my life!

    2. mean, they just check every address and tell you which ones are real people."

      we need better options for this sentence something like you give them your email list, and if you want more info about your email stuff, and they clean it and give you all this weirdly clear information.

    Annotators

    1. cashes in the items above dashboard 2.1/2.2 soften "Hello, Diego!" section follow-ups; keep the greeting exactly as is 4.1-A hairline chapters between Quick actions / Overview / Recent work 5.1 kicker row with "UPDATED TODAY" on the Recent work card 3.2 pick a watermark policy — this page is where it collides most list-cleaning 5.1 kicker row on the jobs card (47 jobs · updated today) 5.2 signature row at the drawer's end 5.3 Ready badge → teal 7.1 one skeleton strip for the table

      dont knwo what this isç

    2. The motto belongs somew

      lets not use dashboard as the title page or anythign already in the menu highlighted based on which page htey are on. the motto is in the footer on the left and the logo in behing=d as now is delph the octopus

    Annotators

    1. ess carries signals of a poor sending history, the kind that tends to hurt inbox placement rather than help it. We do not spell out exactly which signals (that stays behind the scenes). One of these on its own will not sink you, but as a group they bring a much higher cha

      i still don't get how having bad sender rep is an issue inreceiving an email, there must be other things too this label appears for?

    2. he domain's registration has lapsed, so it is dead and nothing can be delivered.

      exaplin that iit may still have active dns, but human person can'T use i unless htye buy it again or someone else does an creates new inbox

    3. A university or school address, usually real and long-lived but often behind strict spam filters.

      i prefer Schools keep mailboxes alive for years, so old addresses linger and still accept mail. The catch: they sit behind aggressive institutional filters, so a low open rate here is usually the filter, not the person.

    4. il address showed up in a known data breach. Breached inboxes tend to get buried in spam, so even when the person is real their engagement often drops, and some of these addresses quietly get abandoned after the breach. It is not an automatic remove,

      approved

    5. the upside of keeping one is tiny, and the downside is that it drags the deliverability of your whole list, not just this one send.

      i don't think this is true same for the description version , why would sending to somepne who has bad sned er rep be bead for me?

    6. The website won't load (a DNS failure), even though the mail server may still be alive. Mail can sometimes still get through, but a site that's fallen off the internet is a sign the domain may be drifting toward abandoned. Keep sending for now if the mailbox responds, but watch for bounces and don't be surprised if this one d

      approved

    7. The domain has no working website (a 404, or no web DNS), though it may still handle email. Plenty of legitimate senders are email-only, so this isn't fatal, it's a yellow flag that the business could be inactive. Send with a light touch and let engagement and bounces tell you whether anyone's really home.

      approved

    8. The address looks made-up rather than real: all numbers, keyboard mashing (asdf, qwerty), test or filler words, or obvious refusals. These usually come from forms with no confirmation step, where people type junk to get past a gate. Deliverable ones can sit in a low-frequency segment, but anything clearly fake is worth removing, and the real fix is a confirmation step so the junk never lands on your list in the first place.

      approved

    9. address turns up on lots of marketing lists, so the inbox is crowded and your mail competes with everyone else's. It's a real, sendable address, engagement just tends to run lower. To earn attention, make the subject line and timing count and keep the

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    10. This address has the hallmarks of people who tend to hit 'spam' more often than average, based on its pattern and history rather than anything the person has done to you yet. It's still deliverable, so this is a caution flag, not a removal. Only send mail they clearly asked for and expect, keep the unsubscribe obvious and easy, and watch complaints closely, pulling back fast if they climb.

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    11. A government or public-sector address (.gov and the like). These are real and reachable, but they sit behind strict filters built to block bulk and marketing mail, so even a valid inbox may never see a promotional send. Keep them

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    12. The domain's registration has lapsed, so it's no longer live and nothing sent to it can be delivered. Usually the business closed, moved, or simply let the domain go. Remove every address on it. If it was an important contact, look for them somewhere else (LinkedIn, a new address) rather than mailing a dead domain.

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    13. The domain hasn't set up the usual email authentication (SPF, DKIM, DMARC). This doesn't stop you from sending to them, it just tells you the domain owner hasn't locked things down, which makes the domain easy to spoof. Nothing to remove on its own, but if you weren't expecting this signup it's worth a second look, because a fake address is more likely to hide behind an unauthenticated domain. Keep by default and let other signals decide.

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    14. The domain is missing the basic security setup a maintained domain normally has, which usually means nobody is actively looking after it anymore. Abandoned domains drift toward trouble over time and are a poor bet to keep sending to. Remove these unless you have a specific reason to believe the domain is still care

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    15. The domain's registration runs out within the next 30 days. If the owner doesn't renew it, the whole domain stops working and every address on it goes dead, so this is a short clock, not a permanent problem. If the contact matters, reach out now while mail still lands and ask for a longer-term address, and re-check the domain in a month. If they renew, the flag clears on its own.

      lets add everything missing from why it matters and how to that isn't already in report text and lets do this then the merge and write mix of all the descriptions nd the longer smart though provoking report description please

    16. s email is invalid, contains a typo in the domain (like gmial.com instead of gmail.com), or shows characteristics of a spam trap. These addresses cannot receive email or are dangerous to send to. Remove immediately. If it's a typo, the email will bounce. If it's a trap, sending damages your reputation. Either way, do not send.

      approved

    17. s email address appears on many marketing lists and likely receives high email volume. Engagement rates may be lower because your email competes with many others in their inbox. Expect lower engagement. To stand out: (1) Use compelling subject lines. (2) Send at optimal times. (3) Personalize content. (4) Consider this a 'harder to reach' segment.

      dont make it as a list, as a apragraph, use lets add everything missing from why it matters and how to that isn't already in report text too

    18. belongs to a government agency or public institution (.gov). These emails are legitimate but often behind strict security filters that may block marketing or bulk messages. No action required - informational label. Be aware that government email se

      remo dash and update sentence to accomodat this change

    19. mail's domain lacks proper email authentication (SPF, DKIM, DMARC). This doesn't affect your ability to send TO them, but indicates the domain owner hasn't implemented security best practices. Usually safe to send, but note: (1) Domains without authentication are easier to spoof - make sure this signup was legitimate. (2) Ma

      dont make it as a list, as a apragraph, use lets add everything missing from why it matters and how to that isn't already in report text too

    20. eliverable. Time-sensitive risk. Options: (1) Send now while you still can. (2) If important contact, reach out for alternative email. (3) Re-validate after expiration date to see if they renewed.

      write as Paragraph not as a list 123

    21. The address shape looks auto-generated or intentionally fake

      CHANGE TO: The address looks made-up rather than real: all numbers, keyboard mashing (asdf, qwerty), test or filler words, or obvious refusals. These usually come from forms with no confirmation step, where people type junk to get past a gate. Deliverable ones can sit in a low-frequency segment, but anything clearly fake is worth removing, and the real fix is a confirmation step so the junk never lands on your list in the first place.

    22. The domain's website returns a 404 error

      CHANGE TO: The domain has no working website (a 404, or no web DNS), though it may still handle email. Plenty of legitimate senders are email-only, so this isn't fatal, it's a yellow flag that the business could be inactive. Send with a light touch and let engagement and bounces tell you whether anyone's really home.

    23. The domain's website is unreachable (DNS failure)

      CHANGE TO: The website won't load (a DNS failure), even though the mail server may still be alive. Mail can sometimes still get through, but a site that's fallen off the internet is a sign the domain may be drifting toward abandoned. Keep sending for now if the mailbox responds, but watch for bounces and don't be surprised if this one degrades.

    24. The domain shows a 'parked' or 'for sale' page

      CHANGE TO: The domain shows a 'parked' or 'for sale' page instead of a real site, which usually means it's expired, abandoned, or being held by a squatter rather than run by a real business. Mail to it is a coin flip at best. Remove these, because the person or company you thought was there almost certainly isn't sending or receiving from this address anymore.

    25. The domain was registered less than 30 days ago

      CHANGE TO: The domain was registered less than 30 days ago, so it has almost no track record yet. It might be a brand-new business or something short-lived thrown up for a single purpose. Nothing to remove, just watch it: if real engagement develops the flag stops mattering, and if it goes quiet or starts bouncing, treat it as the throwaway it might be.

    26. Domain belongs to a military organization

      CHANGE TO: A military address (.mil). Mail routes through the Department of Defense gateway, which accepts everything at the door but then filters hard inside and often drops what it doesn't like without a bounce, so a real inbox can still silently swallow your mail. Keep them if they're your audience, but treat delivery here as unproven, watch engagement rather than trusting 'delivered', and don't read a lack of bounces as success.

    27. The recipient's mailbox has exceeded its storage quota

      CHANGE TO: The person's mailbox is over its storage limit and can't take new mail right now. Sometimes that's temporary, but an inbox that stays full is usually one nobody empties anymore, meaning abandoned. We'd suppress these by default. If you want to give them a chance, park them in a retry segment and re-check in 60 to 90 days before sending, rather than mailing into a full box now.

    28. Email domain belongs to a defunct or acquired ISP

      CHANGE TO: The address is on a defunct or absorbed ISP (sbcglobal.net, earthlink.net, prodigy.net and similar). These still receive mail, but nobody's really maintaining the service anymore, and many are checked rarely or not at all. On its own it doesn't change the verdict, so keep it, but if it pairs with other caution flags or shows no engagement, lean toward retiring it.

    29. This domain appears on threat intelligence lists

      CHANGE TO: This domain shows up on threat-intelligence lists tied to malware, phishing, or other malicious activity. An address here often means a compromised or throwaway account, and mailing it does nothing good for you. Remove it right away. If it's genuinely someone you know, assume their account may be compromised and find a different way to reach them before sending anything.

    30. This email address appears on many marketing lists

      CHANGE TO: This address turns up on lots of marketing lists, so the inbox is crowded and your mail competes with everyone else's. It's a real, sendable address, engagement just tends to run lower. To earn attention, make the subject line and timing count and keep the content genuinely relevant to them; if they never engage, treat them like any other cold contact and taper off.

    31. This email has characteristics associated with higher spam complaint

      CHANGE TO: This address has the hallmarks of people who tend to hit 'spam' more often than average, based on its pattern and history rather than anything the person has done to you yet. It's still deliverable, so this is a caution flag, not a removal. Only send mail they clearly asked for and expect, keep the unsubscribe obvious and easy, and watch complaints closely, pulling back fast if they climb.

    32. Domain belongs to a government agency or public institution

      CHANGE TO: A government or public-sector address (.gov and the like). These are real and reachable, but they sit behind strict filters built to block bulk and marketing mail, so even a valid inbox may never see a promotional send. Keep them, but expect low reach on anything that looks like marketing, and lead with plain, expected, relevant mail.

    33. The domain registration has lapsed and is no longer active

      CHANGE TO: The domain's registration has lapsed, so it's no longer live and nothing sent to it can be delivered. Usually the business closed, moved, or simply let the domain go. Remove every address on it. If it was an important contact, look for them somewhere else (LinkedIn, a new address) rather than mailing a dead domain.

    34. The email's domain lacks proper email authentication

      CHANGE TO: The domain hasn't set up the usual email authentication (SPF, DKIM, DMARC). This doesn't stop you from sending to them, it just tells you the domain owner hasn't locked things down, which makes the domain easy to spoof. Nothing to remove on its own, but if you weren't expecting this signup it's worth a second look, because a fake address is more likely to hide behind an unauthenticated domain. Keep by default and let other signals decide.

    35. The domain lacks basic security configuration and shows signs

      CHANGE TO: The domain is missing the basic security setup a maintained domain normally has, which usually means nobody is actively looking after it anymore. Abandoned domains drift toward trouble over time and are a poor bet to keep sending to. Remove these unless you have a specific reason to believe the domain is still cared for.

    36. The domain's registration expires within 30 days

      CHANGE TO: The domain's registration runs out within the next 30 days. If the owner doesn't renew it, the whole domain stops working and every address on it goes dead, so this is a short clock, not a permanent problem. If the contact matters, reach out now while mail still lands and ask for a longer-term address, and re-check the domain in a month. If they renew, the flag clears on its own.

    37. is is a role-based email (info@, support@, sales@, etc.) rather than a personal address. Role accounts are shared inboxes with higher complaint risk because

      approved. we can add a "cta" to decide if they wan to send to all the role accon=unts, or remove people that might not be the same or interested?

    38. This is a role-based email (info@, support@, sales@, etc.) rather than a personal address. Role accounts are shared inboxes with higher complaint risk because multiple people access them. Consider your use case. For marketing: send less frequently, expect higher complaints. F

      lets add everything missing from why it matters and how to that isn't already in report text too in this definition

    39. his email shows reputation risk signals such as reputation-risk address characteristics or reputation-risk patterns. Sending may damage your sender reputation.

      this means nothing, can e make it ore clear without being specific?

    40. This email is from a legitimate privacy/forwarding service like Apple Hide My Email, Firefox Relay, AnonAddy, or SimpleLogin. These forward to the user's real inbox - the person is reachable but privacy-conscious.

      remove the dashes, and explain what that means for them simply put? harder spam filters, lower thresholds?

    41. This is a temporary/disposable email address. These addresses self-destruct or become inaccessible after a short time. The person wanted your offer but not an ongoing relationship. Remove from marketing lists. Consider: the person may have wanted a one-time download (PDF, resource). You may allow the signup and deliver gated content, but skip follow-up emails.

      lets add everything missing from why it matters and how to that isn't already in report text

    42. The domain has no mail server (MX records) configured. This means there's no technical capability to receive email at this domain. The domain might exist as a website but cannot receive email. Remove all emails from this domain immediately. There's zero chance of delivery. If this is a known contact, reach out through other channels to get an updated email.

      how is this different from invalid email? no mx records is als invalid email no? (the same as Invalid/Typo/Trap no?)

    43. The domain's website shows a "coming soon" or placeholder page. The domain is active and connected, but no real website content exists yet. This might indicate a new business or inactive project. Usually safe to send. The domain is functional, just not fully launched. Monitor for changes - if the site never launches, the business may have stalled.

      Some of these mght be new domains that have automatically adde mx records but not real person, or there is a real person they just donM 't on'T care about having a website

    44. The mail server accepts all incoming email without verifying if specific mailboxes exist.

      lets add everything missing from why it matters and how to that isn't already in report text Accept-All is high. Be smart about how you read "delivered" About 21% of this sample is on Accept-All servers. For B2B outreach this is normal (lots of corporate Microsoft 365 / Mimecast / Proofpoint behind those domains), but it means a "delivered" status from your sending tool is NOT the same as "the inbox actually exists." Mailbox providers will silently drop unknown addresses on accept-all servers, and those failures show up as zero engagement, not as bounces. Watch click rates per domain. Accept-All domains with consistent 0% clicks across multiple campaigns are likely dead boxes.

      Accept-All 412 emails Accept-all mail servers say yes at the connection level without revealing whether a specific mailbox is active. Our checks can verify some of these addresses directly, but not all of them depending on how the server is configured. Consumer providers like Yahoo and AOL often run in accept-all mode, and on business domains this usually comes from security gateways such as Proofpoint, Mimecast, or Barracuda sitting in front of the real inbox. We tag every address on an accept-all server so you can track them as their own segment and watch how they behave in your campaigns. Segment these addresses into their own group and send to them separately from your other contacts. Track their engagement (opens, clicks, replies) over a few sends. Addresses that engage can be moved into your main list with confidence. Addresses that never engage after multiple sends are safe to segment aside for re-engagement campaigns or suppression, depending on your goals.

      66% of this list is in great shape to send to For a combined tax marketing and booking customer list, the validation profile is healthy. Only 29 of 598 addresses (4.8%) need removal. The Monitor segment is mostly Accept-All on consumer providers like Yahoo and Hotmail, where the addresses are real but the providers respond conservatively to validation queries. These should still be sent to. Accept-All 123 emails Accept-all mail servers say yes at the connection level without revealing whether a specific mailbox is active. Our checks can verify some of these addresses directly, but not all of them depending on how the server is configured. Consumer providers like Yahoo and AOL often run in accept-all mode, and on business domains this usually comes from security gateways such as Proofpoint, Mimecast, or Barracuda sitting in front of the real inbox. We tag every address on an accept-all server so you can track them as their own segment and watch how they behave in your campaigns. Segment these addresses into their own group and send to them separately from your other contacts. Track their engagement (opens, clicks, replies) over a few sends. Addresses that engage can be moved into your main list with confidence. Addresses that never engage after multiple sends are safe to segment aside for re-engagement campaigns or suppression, depending on your goals.

      Accept-All 19,281 emails Accept-all mail servers say yes at the connection level without revealing whether a specific mailbox is active. Our checks can verify some of these addresses directly, but not all of them depending on how the server is configured. Consumer providers like Yahoo and AOL often run in accept-all mode, and on business domains this usually comes from security gateways such as Proofpoint, Mimecast, or Barracuda sitting in front of the real inbox. We tag every address on an accept-all server so you can track them as their own segment and watch how they behave in your campaigns. Segment these addresses into their own group and send to them separately from your other contacts. Track their engagement (opens, clicks, replies) over a few sends. Addresses that engage can be moved into your main list with confidence. Addresses that never engage after multiple sends are safe to segment aside for re-engagement campaigns or suppression, depending on your goals. all incoming mail at the gateway but may silently discard messages that don't pass security checks. Monitor carefully. Military domains accept all email at the gate (accept-all) but have aggressive internal filtering. Bounces may not be reported, making it hard to detect delivery failures.

      Accept-All 1,320 emails Accept-all mail servers say yes at the connection level without revealing whether a specific mailbox is active. Our checks can verify some of these addresses directly, but not all of them depending on how the server is configured. Consumer providers like Yahoo and AOL often run in accept-all mode, and on business domains this usually comes from security gateways such as Proofpoint, Mimecast, or Barracuda sitting in front of the real inbox. We tag every address on an accept-all server so you can track them as their own segment and watch how they behave in your campaigns. Segment these addresses into their own group and send to them separately from your other contacts. Track their engagement (opens, clicks, replies) over a few sends. Addresses that engage can be moved into your main list with confidence. Addresses that never engage after multiple sends are safe to segment aside for re-engagement campaigns or suppression, depending on your goals. ✓ 3,159 addresses are clean and safe to send first The Keep bucket is deliverable-only. Every risky, low-confidence, and accept-all-without-a-website address has been pulled out into Monitor or Suppress, so what is left in Keep is what a fresh sender can lead with.

      One ask: if any of these bounce because the mailbox genuinely does not exist (a true "no such user" bounce, not a blocklist or content block), tell us at lists@reviewmyemails.com and we will credit 2 emails back. It helps us learn and improve the checks, and you get the credits. 1,885 addresses are real but need care (Monitor) Monitor is where the address is real but comes with a caveat, and the decision on each is yours. Some sit on accept-all servers: we confirmed the domain is live and its mail server responds, but the server says "yes" to every address at the connection level, so the one specific mailbox cannot be confirmed active by any tool. That is their server's setting, not a gap in our check. Another 1,334 verified as real but with lower delivery confidence. Many of these domains also sit behind security gateways like Proofpoint, Mimecast and Barracuda that only let mail through from senders they already trust, so even a real, active inbox can block a cold sender until you are recognised or allowlisted. A few carry other flags (breach history, a shared role inbox, heavy mail volume), each explained per label below.

      Go label by label below and decide what fits your risk tolerance: som e are worth sending to with care, others you may prefer to hold back. Either is a valid choice. Accept-All 1,416 emails These sit on a server that says "yes" to every address at the connection level, so we cannot confirm whether the individual mailbox actually exists. That is the key difference from Low Delivery Confidence, where we did get a mailbox-level answer. Consumer providers like Yahoo and AOL run this way, and on business domains it usually comes from a security gateway (Proofpoint, Mimecast, Barracuda) sitting in front of the real inbox. We tag every accept-all address so you can track them as their own segment. Do not blast these. Sprinkle a few into your sends over time rather than hitting them all at once, use a shorter sequence with bigger gaps between emails, and cut them off faster if they show no engagement. The ones that do engage can move into your main list; the rest you set aside. Low Delivery Confidence 1,281 emails We checked these mailboxes and they came back real, but with a "risky" signal. This is the key difference from Accept-All: with Accept-All the server accepts everything and hides whether the specific mailbox exists, whereas here we did get a mailbox-level answer, it just was not a clean pass. It usually means the domain or provider has a weaker sending reputation, or the domain is small and low-traffic. These are worth sending to, just keep a close eye on them: track opens and bounces, and drop any that hard-bounce on the first touch. Yahoo and AOL cannot be individually verified, and that is normal These providers run accept-all servers: they say "yes" to every address at the connection level, so no tool can confirm one specific mailbox. That is their server's design, not a gap in the check. Since these subscribers opted in, keep them, but Yahoo and AOL are strict on complaints, so send consistently and prune anyone who never opens.

      Accept-All 609 emails Accept-all mail servers say yes at the connection level without revealing whether a specific mailbox is active. Our checks can verify some of these addresses directly, but not all of them depending on how the server is configured. Consumer providers like Yahoo and AOL often run in accept-all mode, and on business domains this usually comes from security gateways such as Proofpoint, Mimecast, or Barracuda sitting in front of the real inbox. We tag every address on an accept-all server so you can track them as their own segment and watch how they behave in your campaigns. Segment these addresses into their own group and send to them separately from your other contacts. Track their engagement (opens, clicks, replies) over a few sends. Addresses that engage can be moved into your main list with confidence. Addresses that never engage after multiple sends are safe to segment aside for re-engagement campaigns or suppression, depending on your goals.

    1. Single-check "Recent checks" history panel (7 entries, "kept for 60 days")Mongo results have a 60-day TTL ✓, but a per-user single-check history endpoint could not be confirmedKeep the design verify data exists — real frontend has a HistoryResultCard, confirm its source (may be client-side only)

      i donT' know how to check htis

    2. ng pricing slider/presets hardcoded ($0.0062/email etc.)GET /billing/pricing returns real tier boundaries + POST /billing/calculate prices any quantity

      dont know what that means. is it bad? its jsut to show templates in react to devs for reskin, and some corrections

    3. Team invite roles "Admin / Member" onlyBackend supports Owner + permission_template: read_only | validator | member and per-permission flagsEither add the templates to the dropdown or explain Owner somewhere (table shows one)

      sure we can make pop up contact your admin

    4. job rows are unnamed <button>s (screen reader hears "button" ×10); div-tables expose header cells as plain generic nodes (no columnheader/row roles, no aria-sort); confirm-email and reset-password each contain three <h1>s; api-docs jumps h2→h4; dashboard has zero alt text. Each is a one-line fix; do them as a sweep.

      we can fix those accross the board too right?

    5. Every purchase path lands on the billing-purchase.html stub; sidebar "Billing" (Pricing & Plans) vs settings tab "Billing" (Billing Settings) are two different pages with one name; dashboard-states/onboarding sidebars link everything to # and omit Settings while adding "Analytics" (sender-profiles' sidebar also sneaks "Analytics" in); error pages drop the whole app shell. Normalize the nav from one shared partial.

      yea i agree billing setting should just be in billinf and sender preference should be in same place as notification we already have notdsa bout this and other things

    6. e wins sitting in existing responses: credits_saved + cache_hit_count (the "we didn't re-charge you" story), queue_position / estimated_completion / full progress steps with ETA, estimated_credits_min/likely/max for uploads, days_remaining_at_current_rate for billing, the per-job health score + badge + callouts, unique_domains + top_flagged_domains in the results breakdown, typo_suggestion / did_you_mean, segmented downloads (keep|monitor|suppress|did_you_mean + ZIP), and API-key last_used_at / usage_count / expires_at. Individual suggestions below.

      ok no problem to all

    7. Credit pill says 8,450 on most pages, 1,000 on dashboard-states/onboarding, 8,449 on single-check; billing.html's low-balance banner says the balance is 820 in the same viewport as the 8,450 pill; billing-history's newest "Balance After" is 58,450; list-cleaning-new claims You need 40,450 more credits while showing cost 5,200 vs balance 8,450. Pick one coherent demo account state and thread it through every page.

      ok sure we can fix that easy

    8. e scaffolding is leaking into the product surface. "Prototype state:" switchers, the floating 🆕 New pattern badge (login, 404, api-docs, settings-api-keys), Preview — sample data captions, and design-spec prose rendered as body copy (settings-api-keys: In the app this dialog opens centered over a page scrim…; team.html: Cancel invitation confirms the same way…; sender-profiles: Shown open for the handoff…). Fine for handoff review — but tag them all with one consistent data-proto wrapper/class now so they can be stripp

      i don't knwo what this emeans

    9. job-status vocabulary, please. The backend enum is pending · queued · processing · completed · failed · cancelled (rme-backend/app/models/postgres/job.py). The reskin uses three different sets: dashboard badges say Done / Cleaning / Uploaded / Failed, list-cleaning badges say Complete / Cleaning / Ready, and the list-cleaning status filter offers Completed / Processing / Queued / Failed / Cancelled — so the filter options never match the badges beside them. Pick one display mapping (e.g. Queued

      lets update our front end to say the same thing like the backend says add that to glossary with description that are short but explian well what each process means

    10. 2 · Verdict & label terminology drift. Canonical backend verdicts are keep / monitor / suppress. The reskin mostly says "To Keep / To Monitor / To Suppress" (good), but: the dashboard chart legend shortens to "Keep / Monitor / Suppress", api-docs.html says safe, monitor, suppress, glossary prose says "Temporary Email" where the profile editor and single-check say "Disposable", and 403.html says "team admin" where team.html distinguishes Owner/Admin. One glossary of terms, applied everywhere. (The 29-label glossary set also doesn't match any of the three label sources in the codebase — see the drift table below.)

      Let tell the devs to update it then To Keep, etc