Toolsky

Free Online Tools & Utilities for Every Task.

HTTP Methods Auditor

Check which HTTP methods are enabled on a server to identify potential security risks.

GET and POST do almost all the visible work of the web, but they are two members of a larger family. A server can also answer PUT, DELETE, TRACE, PATCH and other HTTP methods — and if methods that were never meant for the public are left enabled, strangers gain abilities your site never intended to offer, such as uploading, altering or deleting content. An HTTP methods auditor checks which methods a server actually accepts and reports them back, so you can compare what is switched on against what your site genuinely needs.

The Methods, and Which Ones Deserve Scrutiny

Each method is a verb the client asks the server to perform. GET retrieves, POST submits, HEAD asks for headers only, and OPTIONS asks the server which methods it supports — the answer to that last one is the backbone of this audit. The scrutiny belongs to the rest. PUT asks the server to store the content sent to it; DELETE asks it to remove a resource; TRACE echoes the request back and has a known history in cross-site tracing attacks; PATCH applies partial modifications. On a correctly configured public website, those four are normally refused for anonymous visitors, because the applications that legitimately use them — APIs, content management back ends — expect authentication and strict handling. An audit does not declare a server vulnerable just because a method answers; it gives you the inventory, and the inventory is what lets you ask the only question that matters: does anything public-facing here accept verbs it should not?

What This Auditor Reports

  • The methods a server accepts: a per-method result for the URL you test, showing which verbs receive a real response rather than a refusal.
  • Evidence from the Allow header: where the server publishes its own list of permitted methods, the auditor surfaces it, so claims can be checked against behaviour.
  • Attention on the risky set: PUT, DELETE, TRACE and PATCH are the methods the report makes easiest to spot, since those are the ones that change or expose data.
  • A repeatable baseline: the same check can be run after any server change, migration or update, turning a one-off look into an audit habit.
  • Plain-language results: you do not need to hand-craft requests with a command-line tool to get the answer — the probing and the reading are done for you.

A methods audit is one panel of a wider security review: combine it with the security headers auditor to check the browser-facing protections, and with the open port checker to see which services the host exposes at all.

How to Audit a Server's HTTP Methods

  1. Enter the full URL of the site or application you want to examine — one you own or are authorised to test.
  2. Run the audit and wait while each method is tried against the server.
  3. Read the results method by method, noting which of PUT, DELETE, TRACE and PATCH are answered rather than refused.
  4. Compare the findings with what the site actually does: a static brochure site needs none of the write methods publicly available.
  5. If risky methods are enabled, restrict them in your server configuration or application rules, limiting them to authenticated paths where they are genuinely required.
  6. Re-run the audit after the change to confirm the methods are now refused.

What an Audit Typically Uncovers

A small business site built on a default server installation is checked for the first time. GET, POST, HEAD and OPTIONS respond as expected. But TRACE also answers — a leftover of the default configuration nobody reviewed — and the web framework's development settings mean PUT requests to an upload path reach code that was written assuming only the admin panel would ever call it. Neither finding is, by itself, proof the site can be breached; both are doors the owner did not know were unlocked. The remedies were configuration-level: disable TRACE at the server, restrict the write methods to the authenticated admin path, and re-audit to watch them refuse. This pattern — defaults plus assumptions — accounts for most of what method audits find, and it is exactly why the check belongs in the routine after any new deployment, not just after an incident.

Responsible Use, Limits and Next Steps

Only audit systems you own or have explicit permission to test. Probing other people's servers can breach their terms and, in some jurisdictions, the law — this is a tool for administrators reviewing their own infrastructure. An enabled method is a question, not a verdict. A well-built API may accept PUT and DELETE safely because every call is authenticated and authorised; the auditor reports exposure, and judging it requires knowing the application. Method handling can differ per path. The root of a site may refuse PUT while an API route accepts it by design, so test the important paths individually rather than treating one URL's result as the server's whole truth. The Allow header can lie politely. Some servers publish an incomplete list or answer OPTIONS generically; that is why the auditor tests behaviour rather than trusting declarations alone. When findings need fixing, the changes live in web server configuration — Apache's Limit and LimitExcept directives or Nginx location rules that pass only chosen methods to the application — and the response each method receives is defined by the status codes described in the HTTP status code checker.

Frequently Asked Questions About HTTP Methods

Which HTTP methods should a normal public website allow?

For anonymous visitors, typically GET, HEAD and POST (where forms or uploads require it), plus OPTIONS for capability queries. Write-oriented methods such as PUT, DELETE and PATCH belong behind authentication, and TRACE is usually disabled entirely.

Why is TRACE considered dangerous?

TRACE makes the server echo the request it received. Combined with other weaknesses, that reflection historically enabled cross-site tracing attacks that could expose headers, including cookies. Modern browsers block some of the technique, but the method serves no public purpose, so disabling it remains standard advice.

Does an enabled PUT method mean my site is hacked?

No. It means the server accepts the verb; whether anything dangerous happens depends on what code handles the request. Many findings turn out to be harmless defaults — but each one should be a deliberate decision, not a surprise.

What is the Allow header?

It is a response header in which the server lists the methods it permits for a resource, most often sent in reply to an OPTIONS request. Auditors compare that declaration against what the server actually does when each method is tried.

How do I disable unwanted methods?

At the server layer: Apache can restrict verbs with Limit/LimitExcept rules, and Nginx can return 405 for methods outside a chosen set in its configuration. Application frameworks often have their own routing controls as well. Always re-test after changing configuration.

Can I audit an API with this tool?

Yes — APIs are where method discipline matters most, because they intentionally use PUT, PATCH and DELETE. The audit shows which methods each endpoint accepts publicly; you then judge that against the API's authentication design.

How often should a methods audit be repeated?

After anything that changes the server's surface: migrations, framework upgrades, new applications on the same host, and configuration edits. Defaults have a habit of returning when software is reinstalled.

Know Your Server's Verbs

A website speaks more verbs than its visitors ever use. Auditing them takes minutes, and the result is a short, concrete list: what is open, what should not be, and what to close. Run it on your own infrastructure whenever the configuration changes, and let no method stay enabled by accident.