security.txt (RFC 9116) in Title and closing
It tells a researcher where to report a vulnerability instead of guessing.
1 of 11 vendors we measured here publish it, that is 9%. Last checked 2026-09-03.
9% here against 13% across every category we measure. Title and closing sits below the overall share for this criterion.
Back to security.txt (RFC 9116) across all categories, or to Title and closing.
Published
Served at /.well-known/security.txt.
| Vendor | What we found |
|---|---|
| Closinglock | https://closinglock.com/.well-known/security.txt |
No security.txt found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| AtClose | 1 address checked |
| Blueprint Title | 1 address checked |
| CertifID | 1 address checked |
| DocMagic | 1 address checked |
| Doma | 1 address checked |
| E-Closing | 1 address checked |
| Endpoint | 1 address checked |
| Proof | 1 address checked |
| PropLogix | 1 address checked |
| SafeDocs | 1 address checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
| Vendor | What we found |
|---|---|
| ClarityFirst | None of the addresses could be reached, so this was not measured. |
Found something we missed? Tell us and the next run picks it up.