CLAUDE WATERMARK REMOVER · DESTINATION TEST
Why did port 443 disappear from my cleaned HTTPS URL?
The URL parser normalizes the default HTTPS port away; port is empty and href omits it.
What the test establishes
The source URL contains a synthetic marker inside its numeric port. Cleanup removes that marker but leaves the explicit digits in the resulting string. Only the subsequent URL parsing and serialization remove the default port notation. Compare the callback output with href to locate that transformation correctly. An empty port getter here represents the default-port serialization contract, not evidence that the cleaner deleted the port digits.
Reproduce the observation
Save tested-app.js and reproduce.cjs together, then run node reproduce.cjs. Compare its output with the recorded observation. The harness executes the actual homepage callback in a minimal DOM and records its resulting field values and method calls. Destination operations run in Node.js; the homepage DOM is a controlled substitute. Runtime: v24.22.1. No submitted text or genuine Claude output is used.
{
"cleaned": "https://example.com:443/a",
"port": "",
"href": "https://example.com/a"
}Capability boundary
The example covers HTTPS and port 443 only. It does not test network connectivity, nondefault ports or invalid-port setter behavior.
This Claude watermark remover edits a small selected character set. These callback observations do not establish authorship, detector scores, statistical-watermark removal or end-to-end browser behavior. For real work, keep the original and compare the exact result at its destination.
Primary material and next step
The tested first-party source snapshot and complete harness are the primary material for this page. For broader scope, read invisible Unicode versus AI watermarks, or return to the cleaner.