Яндекс.Метрика

Unsafe forms checker

Find forms on HTTPS webpages that submit data to insecure HTTP URLs.

0 of 0 ratings

What this checker does

The unsafe forms checker looks at an HTTPS webpage and finds forms whose action attribute points to an insecure HTTP URL. When a form on a secure page submits to an HTTP endpoint, the data travels without encryption, even though the page itself was loaded over HTTPS.

The tool lists the forms that match this pattern so you can review and correct them.

Why this matters

Users trust the padlock icon and the HTTPS indicator. If a form on that page sends data to an HTTP endpoint, the submission is not protected in transit. Depending on the browser and configuration, the submission may be blocked, downgraded, or allowed with a warning.

Forms often carry sensitive information: names, email addresses, messages, login credentials, or payment details. Sending that data over plain HTTP exposes it to interception on the network.

Browsers increasingly treat mixed content as a security issue. Some submissions may fail silently or produce confusing errors for users, which harms conversion and trust.

How insecure form actions happen

  • Legacy endpoints: an old backend still uses an HTTP URL that was never updated.
  • Hardcoded actions: templates or plugins specify http:// directly instead of a relative or protocol-relative path.
  • Third-party services: an external form handler is configured with an HTTP endpoint.
  • Copy-paste errors: a form was duplicated from an older page and the action was not updated.

Reading the results

The checker reports forms whose action is an absolute HTTP URL. It does not submit the forms, test the endpoints, or verify that data is actually sent insecurely after JavaScript processing. It reports what the HTML declares.

If no unsafe forms are found, the page’s forms either use HTTPS, relative paths, or no action attribute. Relative paths inherit the page’s protocol, so they are generally safe on an HTTPS page.

Practical guidance

  • Use HTTPS endpoints: update the action to an HTTPS URL that supports the same functionality.
  • Prefer relative or protocol-relative paths: an action like /submit avoids hardcoding the protocol.
  • Check third-party handlers: confirm that external form services support HTTPS and update the configuration.
  • Test after changes: submit the form and confirm the data arrives correctly and no browser warnings appear.

Limitations

The checker examines the HTML returned for the URL you provide. Forms generated or modified by JavaScript may not be detected. It does not validate the security of the destination endpoint beyond its protocol, and it does not check whether the endpoint itself is trustworthy.

Use the results to find and fix insecure form actions, then verify the full submission flow in a browser.

Similar tools

Mixed content checker

Find insecure HTTP resources referenced by an HTTPS webpage.

9
SSL Lookup

Inspect an SSL/TLS certificate: issuer, validity dates, common name and signature type.

0
Safe URL checker

Check whether Google flags a URL as safe or potentially unsafe for visitors.

12

Popular tools