Question 1

What does Brinkmote monitor?

Accepted Answer

Brinkmote reviews the public edge around a submitted domain: public DNS records and related names, HTTP and HTTPS behavior, TLS certificate signals, and bounded reachability of public services. It turns those observations into plain-language findings for your team to review.

Question 2

Does Brinkmote check HTTP, HTTPS, and TLS?

Accepted Answer

Yes. The public checks review how a domain responds over HTTP and HTTPS and inspect basic TLS certificate signals, such as whether a certificate matches the hostname and whether it remains current. The result is a starting point for review, not a full certificate or application audit.

Question 3

What does bounded public service reachability mean?

Accepted Answer

Brinkmote checks a defined, limited set of publicly reachable service signals around the submitted domain. That can surface an exposed admin, remote-access, database, or alternate web service worth confirming; it is not exhaustive network discovery.

Question 4

Who can submit a domain?

Accepted Answer

Only submit a domain you own or are authorized to assess. You are responsible for having permission before starting a public-surface review, including when the domain belongs to a customer, vendor, or another organization.

Question 5

What happens after a domain is submitted?

Accepted Answer

Brinkmote creates a scope from the submitted domain and runs the public checks against that scope. The resulting observations are organized in the workspace so your team can review the domain, affected hostname or service, and any findings that need attention.

Question 6

What is a finding?

Accepted Answer

A finding is a public signal that deserves a closer look, shown with context such as the affected hostname and the check that produced it. A finding is a prompt to verify and prioritize; it is not, by itself, proof that a system has been compromised.

Question 7

How are findings prioritized?

Accepted Answer

Brinkmote presents findings in a prioritized view to help a small team decide what to confirm first. The ordering considers the observed public signal and its context; it is decision support, not a guarantee of severity or a replacement for your security team, provider, or incident process.

Question 8

How do remediation tasks support follow-up?

Accepted Answer

You can turn an exposure finding into a remediation task, assign ownership, record the next step, and track its status. A later completed scan can show that a finding is no longer observed, while the task history keeps the team’s follow-up visible.

Question 9

Does Brinkmote access private content or internal networks?

Accepted Answer

No. These checks are designed for what is publicly observable from the internet. They do not require passwords, private content, internal network access, or access to your private systems.

Question 10

Does Brinkmote run destructive tests?

Accepted Answer

No. Brinkmote’s public checks are intended to observe and describe reachable signals, not to exploit, alter, or disrupt a system. It is a public-surface review, not a penetration test or a guarantee that a system is secure.

Question 11

What data does Brinkmote not need to perform a public check?

Accepted Answer

A public check does not need passwords, private credentials, private application content, or internal network access. Do not submit secrets or private content for a public-surface review; submit only an authorized domain and the information needed to describe its scope.

Know what your public edge is saying.

The useful version of “what does this actually do?”

What gets looked at

From domain to readout

From signal to next step

What stays private

Start with the domain your team owns.