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 | 213.255.209.181 |
|---|---|
| Reverse DNS | probe.getfullarc-verify.com |
| EHLO / HELO name | probe.getfullarc-verify.com |
| Envelope sender | verify@getfullarc-verify.com |
| Port | Outbound TCP 25 only. This server accepts no mail. |
| Commands | EHLO (or HELO), MAIL FROM, RCPT TO, QUIT. Never DATA. |
Moving to these names.
Until our reverse DNS is in place, connections from the same IP may still introduce themselves as verify.lightlycoded.com, with the sender probe@verify.lightlycoded.com. That is us too.
What to expect
Connections happen when a FullArc customer checks a contact list before an email campaign. Volume is low by design: a definite answer is reused for 30 days, and we wait at least a day before asking again after a refusal or a timeout.
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@getfullarc-verify.com or postmaster@getfullarc-verify.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.