For mail server operators
Full visibility.
Full control.
If your logs show a connection from us, it was checking whether a mailbox exists, not delivering a message. Here is how to recognise it, and how to stop it.
Recognising our connections
We publish these so you can tell our checks apart from mail delivery or from someone pretending to be us.
| Outbound IP | 13.140.47.77 |
|---|---|
| Reverse DNS | probe.inboxreadycheck.com |
| EHLO / HELO name | probe.inboxreadycheck.com |
| Envelope sender | verify@inboxreadycheck.com |
| Port | Outbound TCP 25 only. This server accepts no mail. |
| Commands | EHLO (or HELO), MAIL FROM, RCPT TO, QUIT. Never DATA. |
What to expect
Connections happen when a FullArc customer checks a contact list before an email campaign. Volume is low by design: one address per connection at least 30 seconds apart, a definite answer reused for 30 days, and at least a day before asking again after a refusal or a timeout. An address beginning catchall-check- is our one test of whether your server accepts every address, asked at most once per domain every 90 days.
A verification is not an email.
We stop before DATA. No message is delivered to any mailbox.
Your options
Opt out.
Ask us to stop checking your domain and all its subdomains, or a mail host and every domain it serves. We act on requests within one business day.
Refuse the connection.
That is fine too. We record a refusal as “could not be checked”, never as “invalid”, so your users are not marked as bad addresses. We never change our IP, name or sender to get around a block.
Report a problem
Email abuse@inboxreadycheck.com or postmaster@inboxreadycheck.com. A person reads both and answers within one business day. Log lines with times, and your timezone, help us find the check in question.