starttls-backend
starttls-backend copied to clipboard
STARTTLS Everywhere web backend and checker
we should wait for the validation email to be received & acted on before overwriting the current `domain` entry.
The server may be using the in-app defaults rather than the env to connect to the DB
Right now, this queues folks domains in `testing` mode by default. Let's open up a pathway in the back-end for people to request `enforce` without having to do it through...
Currently, we make two concurrent connections to a mail server during a hostname check. Making those connections sequential might help avoid aggressive anti-spam measures.
Currently, we dump all the scans as blobs into a table, and right now we only support querying the most recent scan for a domain. let's make it possible to...
The same way the main thread is shut down gracefully (#14)
made this separate from #43 since it'll be more involved, including some changes to the checker API, since we only know IPs after the MX lookup.
As according to [RFC2821](https://tools.ietf.org/html/rfc2821#section-5)