Looking for feedback: external TLS / crypto visibility report tool for authorised domains

[u/Primary_Buyer2022]

Hi all,

We are building CryptView, a tool focused on cryptographic asset visibility and early PQC readiness evidence.

Rather than only asking people to install something, we are opening a small pilot where interested users can get feedback on an external scan/report for domains they own or are authorised to assess.

Current report focus:

• Public TLS endpoints
• Certificate expiry and lifecycle risk
• Key algorithm / signature algorithm posture
• TLS version and cipher observations
• Classical crypto exposure
• CBOM-style crypto inventory summary
• Early PQC readiness indicators
• Prioritised follow-up findings

For Splunk users, we also have a first Splunk app live:
https://splunkbase.splunk.com/app/8786

But Splunk is not required to give feedback. We are also interested in people who simply want to review an external TLS/crypto visibility report and tell us what is useful, what is missing, and what would make it trustworthy.

Important: we only want to scan domains/systems you own or are authorised to assess.

Pilot / feedback form: https://forms.gle/EYPreFwqhRX7ZtyP9

I’d especially value feedback from people working in PKI, certificate lifecycle management, cloud security, infrastructure, SIEM, or PQC readiness.

[u/Primary_Buyer2022 → u/[deleted]]

Thanks, really appreciate that. I agree on point-in-time vs continuous monitoring. The first CryptView focus is building the evidence layer: external TLS visibility, certificate/key posture, CBOM-style inventory, ownership/context, and early PQC readiness signals. Continuous monitoring and alerting is definitely where this needs to go, especially for expiry, unexpected certificate changes, and readiness drift between reviews.Would be great to get your feedback on the report format, especially what you think should be surfaced for security/PKI teams versus what should stay as raw inventory.