SUPPORT
Support
Answers to the questions that come up most often, and how to reach a person when they do not cover it.
Contact
Email info@coldemailinboxes.io. We reply within one business day, and usually sooner.
For a problem with a specific batch, include the domains involved and what you are seeing. For a deliverability question, run the domain through the DNS records checker first and send the result - it answers most of what we would ask.
Common questions
Check authentication first, because it is the most common cause and the easiest to verify. Run the domain through the DNS records checker: SPF should resolve without exceeding ten DNS lookups, DKIM should return a key on selector1 and selector2, and DMARC should exist. If all three pass, the issue is usually volume or content rather than infrastructure - ramp slowly and vary your copy.
Most resolvers pick up new records within minutes, but the TTL on any previous record governs how long the old value is cached. Records that never existed before appear quickly, which is the ordinary case here; records that are being changed can take longer, because the old value stays cached for its TTL. This is why deployment is quoted at 24 to 48 hours rather than same-day.
Each inbox is provisioned for three emails per day, and that limit exists for a reason. New mailboxes with no sending history are treated with suspicion, so ramp gradually in your sequencer over two to three weeks rather than starting at the cap on day one.
Every inbox works with OAuth or an app password over standard IMAP and SMTP. Smartlead, Instantly, Lemlist, Woodpecker, Reply.io and Apollo are all confirmed to work. If your platform accepts standard credentials, it will work too.
Microsoft 365 publishes DKIM at selector1 and selector2, but the keys are only active once DKIM signing is enabled for the domain in the tenant. If the checker finds no key, signing has usually not been switched on yet, or the CNAME records have not propagated. Both are part of the setup we complete before handoff.
p=none only monitors: mail failing authentication is still delivered. That is a reasonable starting point while you confirm every legitimate sender passes, but it provides no protection against spoofing. Once your reports are clean, move to quarantine, then to reject.
Yes, at no extra charge. We strongly suggest not using your primary corporate domain for cold outreach: reputation damage there affects your real business mail. Use dedicated domains that can be retired without consequence.
You own them. Domains are registered to you, and the credentials are yours. There is no lock-in and nothing stops working if you stop ordering.
Check which list using the blacklist checker, then request delisting through that provider directly - each maintains its own process. Address what caused the listing first, since delisting a domain that is still sending badly only resets the clock.
Diagnose it yourself
The DNS records checker reports SPF, DKIM, DMARC and MX for a domain in one pass, including the SPF lookup count that silently breaks records once it passes ten. It takes a bulk list too, so you can audit a whole batch at once.