Who builds DomainLens
No company behind this and no funding round. Two people who kept running the same reconnaissance by hand and decided the merged, resolved, scored version of it should simply exist — one on the interface and the infrastructure, one on the API underneath it.
Idea, interface and DevOps
Started DomainLens from a plain annoyance: certificate transparency search hands you a wall of names and leaves the actual work — filtering, grouping, working out what still resolves — to you. Designed and built every page on this site, and works the DevOps side of it: the pipelines, the environments and the hosting both halves ship to.
Backend and security engineering
Builds the API this site is a client of — the provider fan-out, the merge and de-duplication, DNS resolution, certificate matching and the passive hygiene score. Works in information security day to day, on ISMS and ISO 27001 practice, and is preparing for the OSCP.
How the two halves meet
The split is clean, and the seam between the halves is one documented HTTP contract. Every panel this site renders is a call to the aggregation API, so the same data is available to you on the same terms — no key needed to read, and no private endpoint the UI gets that the reference does not describe.
Free to use, and it costs us something
Provider quotas, resolvers and hosting come out of pocket. If DomainLens saved you an afternoon, a coffee helps keep lookups anonymous and free for the next person.
