WebDAV Connection Tester

Verify that your WebDAV server is reachable and responding correctly. Tests with a real PROPFIND request and reports the server’s DAV compliance level.

Include the full URL with path, e.g. https://cloud.example.com/remote.php/dav/

Your credentials are used only to test your server and are never logged or stored.

How the test works

This tool sends a PROPFIND request with Depth: 0 to your URL - the standard WebDAV method for querying a resource’s properties. A healthy WebDAV server responds with 207 Multi-Status.

The DAV response header reveals the server’s compliance level (e.g. 1, 2, 3 or 1, 2, extended-mkcol). If this header is absent, the server may not support WebDAV.

207

Multi-Status - WebDAV is working correctly.

401

Unauthorized - credentials required or incorrect.

403

Forbidden - authenticated but no access to this path.

404

Not Found - path doesn’t exist; try the root or a different path.

Common WebDAV URLs

Most failed tests are the wrong path, not a broken server. The usual addresses:

  • Nextcloud - https://cloud.example.com/remote.php/dav/files/USERNAME/
  • ownCloud - https://cloud.example.com/remote.php/webdav/
  • Synology NAS, with the WebDAV Server package - https://nas.example.com:5006/ over HTTPS, or port 5005 over plain HTTP.

A server with two-factor sign-in usually wants an app password here rather than your normal one.

The test passes, but Windows won't connect

Then the server is fine and the problem is Windows' own WebDAV client, the WebClient service behind Map network drive. It has to be running, it sends passwords only over HTTPS unless you change a registry setting, and it refuses files over 50 MB by default. What is WebDAV, and how to set it up on Windows walks through each fix, and a dedicated client such as FTPie skips the WebClient service altogether.