HTTP POST Test
Use the forms below to send a test message or upload a file to dlptest.com with an HTTP POST over plain, unencrypted HTTP. Load this page and submit the form over http:// and the request stays in cleartext, which is what you want when testing a network tap, a passive Network Monitor, or anything else that inspects traffic without decrypting it. The server reads the request and throws away the body. Nothing is logged, stored, or forwarded.
Testing something that decrypts TLS instead, like an SSL-inspecting proxy, an ICAP integration, or an SSE/SASE agent? Use the HTTPS POST test.
Test with curl or scripts
The endpoint is /api/http-post/. You can POST any body (form data, JSON, raw bytes, multipart). You get JSON back with an ok field, which is true when the body was accepted. A GET on the same URL returns a short JSON hint. This route allows cross-origin requests, so you can call it from automation or from a browser on another site. It's the only route that does.
Examples (use your own hostname for staging or production):
# Probe the endpoint
curl -sS "http://dlptest.com/api/http-post/"
# Small form-style body
curl -sS -X POST "http://dlptest.com/api/http-post/" \
-d "message=DLP+POST+test"
# JSON body
curl -sS -X POST "http://dlptest.com/api/http-post/" \
-H "Content-Type: application/json" \
-d '{"note":"sample payload"}'
# Raw file (single part; good for scripted throughput checks)
curl -sS -X POST "http://dlptest.com/api/http-post/" \
--data-binary @./your-local-file.binKeeping your browser on http://
This site doesn't enforce HSTS, so it never tells a browser to upgrade to HTTPS. Some browsers upgrade http:// on their own anyway, even when you type it in, because the site also answers on HTTPS. Here's what to expect:
- Chrome / Edge: a URL you type with
http://loads in cleartext by default. The address bar shows "Not Secure", which is your confirmation. If you type the domain withouthttp://it may try HTTPS first, so include the prefix. - Brave: upgrades
http://URLs by default, even when you type them, and even in private windows (Shields' "Use secure connections"). To test cleartext, click the Brave Shields lion icon on this page and turn off Use secure connections for this site, or change the global default atbrave://settings/shields. - Firefox: private windows use HTTPS-First by default and only fall back to HTTP when HTTPS fails, which it won't here. Use a normal window, or add an exception if HTTPS-Only Mode is on at
about:preferences#privacy. - Safari: upgrades automatically when it knows a site supports HTTPS, and there's no per-site override. Use another browser, curl, or a script for cleartext testing.
If your browser cached an HSTS policy for this domain from before mid-2026, when this site sent one, one HTTPS visit now clears it (the site sends max-age=0). You can also delete it at chrome://net-internals/#hsts under "Delete domain security policies". Whichever browser you use, confirm the request was really cleartext with a packet capture or your inspection tool's logs. An address bar showing http:// and "Not Secure" is a good sign, but the capture is what proves it.
What is an HTTP POST?
An HTTP POST is a request method supported by the HTTP protocol. By design, the POST request method requests that a web server accept the data enclosed in the body of the request message, most likely for storing it. It is often used when uploading a file or when submitting a completed web form. More info can be found on good old Wikipedia.
Why test over plain HTTP
Most traffic is encrypted now, so it's tempting to treat something that decrypts TLS the same as something that inspects cleartext. They're different controls and they fail in different ways. Some of them, like network taps, passive Network Monitors, and some older proxies, were never built to decrypt TLS at all. Auditors and regulators often expect you to keep testing both, and this page gives you a safe target for it.
How dlptest.com uses POST
Here at dlptest.com we don't store any info from the HTTP POST, but most websites will store your data. The Worker reads the request body so the bytes make it across the network, where your inspection tools can see them, and then throws them away. That means you can test DLP rules, ICAP integrations, and network inspection without sending real customer data to a third party that would keep it.