Perimeter is made by Unlogged. This page exists because you are about to trust a security vendor, and you should be able to find out what kind of company it is before you do.
One product. Perimeter checks the security and compliance posture of a website from the outside — TLS certificate and protocol, HTTP security headers, DNS and email authentication, and the accessibility of the rendered HTML — every day, and emails you when something breaks, expires, or regresses. Every check is read-only and external. We never ask for credentials, never install an agent, and never touch the inside of your systems. The full list of what we inspect, and the dated changelog of every ruleset change, is on the methodology page.
This is the part most vendors leave out, so we will put it first.
What we do give you is a dated, versioned record: every result is stamped with the exact ruleset version that produced it, so months later you can still show what was checked, when, and against which rules.
By subscriptions. That is the whole model. Unlogged is independently owned and funded by the people who build it — no outside investors, and so no pressure to grow at a pace that would make us start selling something other than the product.
We do not run advertising, we do not have a data-brokerage side business, and we do not sell, share, or enrich customer data. We publish aggregate statistics — what percentage of scanned sites are missing DMARC, for instance — but those are counters with no domains attached and nothing about an individual site in them. The privacy policy is the binding version of that promise.
Deliberate. Perimeter is a security product, and the smaller the public attack surface around the people who operate it, the better — that is the same advice we would give any customer. It also keeps the product honest: you should choose Perimeter because the checks are right and the reasoning is published, not because of anyone's founder story.
What we will not do is invent the things we have chosen not to publish. There is no fictional headquarters on this site and no fabricated team page, because a security vendor that lies about small things has told you exactly how much to trust it on large ones.
Email ahsan@getunlogged.com. That address is read by the person who builds the product, not a ticket queue. If you have found something wrong with a check — a false positive, a finding we grade too harshly, a standard we have got out of date — that is the most useful mail we receive, and it is how the ruleset changelog gets its entries.
Free, no account, no email required.