Enterprise access and trust

Information for IT, security and network administrators.

This page documents the public website requirements and product trust information needed to review or allow access to Infracheck in a managed environment.

Website access requirements

• Primary FQDN: infracheck.app
• Redirect alias: www.infracheck.app redirects to the primary FQDN.
• Required port: outbound TCP 443.
• TLS: TLS 1.2 and TLS 1.3 are supported with a publicly trusted certificate.
• CDN and protection: the website is served through Cloudflare. Allowlist by FQDN, not by IP address, because edge addresses can change.
• HTTP: port 80 is used only to redirect to HTTPS and is not required when the HTTPS URL is opened directly.
• Inbound access: no inbound connection to the user device or corporate network is required to browse the public website.

Browser behavior and TLS inspection

The website uses standard HTTPS and does not use browser certificate pinning, a client certificate, a browser extension or a proprietary browser protocol. A managed TLS inspection proxy should present its organization-trusted certificate to the browser and forward the request by hostname. If a connection is reset before an HTTP response is returned, administrators should check the secure web gateway, EDR, VPN and TLS inspection logs for the applicable policy.

HTTP/3 may be advertised by the CDN. Clients that cannot use UDP 443 should fall back to HTTPS over TCP; UDP 443 is not required for access.

Resources loaded by the public website

Page scripts, styles, images and fonts are served from infracheck.app. The website does not require third-party advertising, analytics or tracking domains to render. Optional download links may take the user to:

• play.google.com for the Android app;
• github.com for the Windows and appliance source repositories and published releases.

Access to those external destinations is separate from access to the Infracheck website and can be governed by the organization's normal software-download policy.

Software distribution and integrity

• Android releases are distributed through Google Play.
• Current Windows release executables are Authenticode-signed by ATG Services. Administrators should verify that the signature is valid before deployment.
• The Windows and Docker appliance source repositories are public on GitHub.
• The appliance is customer-hosted and runs inside the customer's environment.
• Legacy or development executables should not be distributed in managed environments.

Product links and the currently supported distribution locations are listed on the download page.

Privacy and website data flow

The public pages do not require an account and do not use advertising trackers. A visitor's browser contacts the Infracheck website to retrieve first-party page resources. Information entered into the contact form is submitted only when the visitor chooses to send it. See the Privacy Policy, GDPR information and Data Safety summary.

Security reporting

Report a suspected vulnerability or security issue to [email protected]. Include the affected URL or product, reproduction steps, observed impact and a safe way to contact you. Do not include credentials, personal data or destructive proof-of-concept material in the initial message.

The machine-readable security contact is published at /.well-known/security.txt.

Connection troubleshooting for administrators

These read-only checks distinguish name resolution, TCP/TLS and HTTP policy failures on Windows:

A successful request returns an HTTPS response from the Cloudflare-served website. If the browser reports ERR_CONNECTION_RESET and the command-line request is also reset, inspect the corporate proxy or endpoint security event at the same timestamp. For allowlisting assistance, use the contact page.

Last updated: 11 August 2026.