Redirect Contract Verifier avatar

Redirect Contract Verifier

Pricing

from $0.003 / redirect verification

Go to Apify Store
Redirect Contract Verifier

Redirect Contract Verifier

Check whether a URL redirects to the destination you expect. Get a deterministic PASS/WARN/FAIL result with the final URL, HTTP status, redirect chain, and reason code.

Pricing

from $0.003 / redirect verification

Rating

0.0

(0)

Developer

Plutonus

Plutonus

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Share

Redirect Contract Verifier follows a bounded chain of public HTTP(S) redirects and checks whether the final destination and HTTP status satisfy one expected redirect contract. It writes exactly one result item to the default dataset.

Input

The Actor accepts exactly two required string fields:

  • source_url: the absolute public HTTP(S) URL where traversal starts.
  • expected_target_url: the absolute public HTTP(S) URL expected after traversal.
{
"source_url": "https://example.com/",
"expected_target_url": "https://example.com/"
}

Result

Each dataset item contains:

  • verdict
  • reason_code
  • source_url
  • expected_target_url
  • final_url
  • final_status
  • redirect_count
  • redirect_chain
{
"verdict": "PASS",
"reason_code": "TARGET_MATCH",
"source_url": "https://example.com/",
"expected_target_url": "https://example.com/",
"final_url": "https://example.com/",
"final_status": 200,
"redirect_count": 0,
"redirect_chain": [
{
"url": "https://example.com/",
"status": 200,
"location": null
}
]
}
  • PASS: the normalized final URL matches the expected target and the final status is 2xx.
  • WARN: the normalized final URL matches, but the final status is 4xx or 5xx.
  • FAIL: the target differs or input, safety, redirect, DNS, timeout, TLS, or HTTP transport validation fails.

Target comparison lowercases and IDNA-normalizes the hostname, removes default HTTP(S) ports, treats an empty path as /, and ignores fragments. Path case, trailing slashes, query content, and query ordering remain significant.

Boundaries

Only public HTTP(S) destinations are allowed. The Actor validates each destination before contact, rejects private and otherwise non-public addresses, detects redirect loops, and limits redirect traversal.

It does not provide browser rendering, authentication, cookies, private-destination access, crawling, monitoring, or AI analysis.

The pay-per-event name is redirect-verification; pricing is configured separately by the operator. Publication requires Limited permissions only.