Frequently asked questions

Dennisen helps users assess whether a domain appears safe, cautionary, or high risk before interacting with it. It combines technical and structural signals into a decision that is easier to understand and act on.

No. Dennisen is a decision support tool, not a guarantee. It helps users make better-informed judgments based on available evidence, but it should not replace organizational policies, security awareness, or additional verification steps when the stakes are high.

Yes, especially through the Security and Enterprise views. However, for sensitive workflows, Dennisen should complement your broader security controls rather than replace them.

Dennisen evaluates signals related to domain identity, registration patterns, DNS, SSL, and structural characteristics. Those signals are grouped and translated into a decision, confidence level, and supporting explanation.

Dennisen looks at factors such as domain structure, possible impersonation patterns, registration age, DNS availability, SSL presence and validity, and other supporting indicators that help establish trust or caution.

A legitimate domain can still receive a caution result if the available evidence is incomplete, mixed, or unusual. For example, a newer domain, missing infrastructure signals, or limited registration visibility can reduce confidence without necessarily indicating malicious intent.

Appears safe means the domain shows consistent trust indicators and no meaningful signs of deception in the observed evidence. Use caution means the signals are mixed, incomplete, or moderately concerning. High risk means the domain shows characteristics commonly associated with phishing, impersonation, or deceptive activity.

Confidence reflects how strongly the available evidence supports the result. High confidence means multiple signals align clearly. Moderate confidence means useful signals are present but not all evidence strongly aligns. Low confidence means data is limited, conflicting, or incomplete.

Treat the result as a prompt for additional verification. Check the domain carefully, review the explanation, compare it with what you know about the source, and use other trusted verification steps if the situation matters.

Consumer is designed for clarity and quick understanding. Security adds deeper signal visibility and technical context. Enterprise adds structured outputs, grouped rationale, audit-ready reporting, and operationally useful detail for teams and organizations.

Dennisen keeps core safety-oriented assessment accessible, while Enterprise adds structured reporting, defensible rationale, and operational value for organizations that need to justify, review, and document decisions at scale.

That is the intention. Dennisen should not hide safety-critical truths behind a paywall. Higher tiers are meant to add structure, reporting, and operational value rather than conceal important risk information.

Dennisen may track aggregate usage metrics and internal analytics to improve the platform, measure performance, and support operational visibility. Public-facing trust signals should remain honest and proportionate to actual usage.

Usage metrics can help communicate that the platform is being exercised in real-world scenarios, but they should be presented conservatively and only once they are meaningful enough to support trust rather than undermine it.

Yes. Feedback is important for improving clarity, catching edge cases, and refining how results are explained. The goal is to build that in a way that supports learning without adding unnecessary complexity too early.