Deliverability Monitoring and Domain Rotation on Evidence

Rotation is a measurement, not a calendar: A domain gets retired when a number says so. Mine: seed placement at Microsoft consumer below 70 percent three days running, Google Postmaster domain reputation dropping a band and not recovering inside a week, or a complaint rate above 0.10 percent, which is a third of the level Google publishes as the ceiling. Rotating on a fixed 90-day schedule throws away domains that were fine and keeps ones that were not. Measured daily: Two seed sends a day through GlockApps and MailReach, across Gmail, Outlook and Hotmail consumer, Microsoft 365 tenants, and the Dutch consumer providers that decide whether your mail reaches a makelaarskantoor at all. Google Postmaster Tools for domain reputation, spam rate and authentication pass rates. Microsoft SNDS and the JMRP feedback loop where the IP is yours. Yahoo's complaint feed. DMARC aggregate reports parsed weekly, which is where an unauthenticated forwarder or a forgotten third party sending as you shows up first. Blocklists worth answering, and one that is not: A Spamhaus SBL listing stops sending the same hour. A CSS listing gets the same treatment, because the step after CSS is worse. Barracuda and SURBL are checked daily and both have working delisting paths. UCEPROTECT level 3 is not chased: it lists entire /24 neighbourhoods, very few receivers filter on it, and the express delisting fee funds the list. When somebody forwards you a red report containing it, I will put that in writing to them. Bounces read properly: A 4.7.x response is a throttle, which is a volume signal, and it is answered by lowering the cap at that provider for a week, not by rotating a domain that has done nothing wrong. A 5.7.1 policy block is content or reputation and stops that segment immediately. Hard bounces above 3 percent stop the campaign and send the list back for verification before another send goes out. Most emergency rotations I am asked to perform are throttles that were misread as failures. The rotation itself: When a domain is retired, its mailboxes stay live for 60 days so replies still land where a person reads them. The domain is parked, the 301 stays, and it never returns to sending, because a rested domain carries its history back with it. Replacement domains are registered at least 30 days before first send and ramped from zero. Two spares stay warm at low volume at all times, which is what makes a retirement a Tuesday rather than an incident. What arrives each week: One page: placement by provider, complaint rate, bounce mix, blocklist state, what changed, what I did about it, and one recommendation. Forty-five minutes on a call monthly. Alerts the same evening when a threshold trips, with the action already taken rather than a question waiting for you. Not included: Copywriting, list verification and list sourcing. Blocklist appeals arising from data bought before we started: I will handle the first one and tell you the second is not worth either of our time. Monitoring of your transactional or newsletter domain is a separate engagement with different thresholds, and I keep the two apart deliberately, because the moment they share a dashboard somebody starts making decisions about invoices based on cold email numbers. Who this is not for: A sender who wants a dashboard that stays green. What you are buying is being told to stop sending on a Thursday morning when the quarter is short, and that call being right. If nobody on your side would act on it, this retainer is decoration and I would rather you kept the budget.