verify.glintscout.com
The Glintscout email check
Glintscout keeps a directory of general business email addresses, such as info@ or sales@, found on businesses' own websites. From time to time it checks whether these addresses still accept mail, so that its customers do not write to addresses that no longer exist. The check asks the address's mail server and never sends a message.
How to recognise it
The check connects from the IP address 65.21.52.231. Its reverse DNS name is verify.glintscout.com, and that name points back to the same address (forward-confirmed reverse DNS), so you can check a connection in your mail server's log:
$ host 65.21.52.231
231.52.21.65.in-addr.arpa domain name pointer verify.glintscout.com.
$ host verify.glintscout.com
verify.glintscout.com has address 65.21.52.231It greets your server with EHLO verify.glintscout.com and gives check@verify.glintscout.com as its sender.
What it does
- It looks up the MX record of the address's domain.
- It connects to port 25 of that mail server and greets it (EHLO).
- It names its sender (MAIL FROM) and the address it checks (RCPT TO).
- When your server accepts the address, it asks about one random address on the same domain, to learn whether the server accepts every address.
- It ends with RSET and QUIT.
In your log, one check looks like this:
EHLO verify.glintscout.com
MAIL FROM:<check@verify.glintscout.com>
RCPT TO:<info@example.com>
RSET
QUITIt starts TLS only when your server requires it.
What it never does
- It never sends a message: it never gives the DATA command, so nothing reaches any mailbox.
- It never logs in, and never asks VRFY or EXPN.
- It never uses proxies or other addresses: every connection comes from the address above.
- It never checks personal addresses, and never the lists Glintscout's customers upload.
How often, and how politely
- An address it got a clear answer for at most once in 90 days. When a server answers "try again later", up to three retries within an hour; an address still without a clear answer is asked again after 2 to 60 days, and after four such answers in a row not before 60 days.
- One connection at a time to each mail server, with pauses between connections.
- At a mail server outside the large providers, at most three refused addresses in ten minutes, so that it never looks like guessing addresses.
- It slows down when a server asks it to. When a provider refuses it, it stops for that whole provider for at least a day; when another mail server refuses it, it stops for that server for at least a day.
What it keeps
Only the result (valid, invalid, accepts every address, or unknown) and the day of the check, never the conversation with your server. How Glintscout uses the directory, and your rights, are described in our Privacy Policy.
How to opt out
- One address, or every address on your domain: ask on the Remove your data page, or with the form below. An address is removed and kept off Glintscout as soon as you confirm with the link we send to it; a domain is confirmed through an address on it and then checked by hand. An address or a domain on that list is never checked, collected or used again.
- You run a mail server and want no checks on it at all? Write to support@
glintscout.com with the name and the IP address of the server, and within two working days it joins the list of servers the check never contacts. The check knows a server by its address too, so the domains whose own MX name points to it are left out as well.
Contact
Questions about the check, or a connection you did not expect? Write to support@