# URL Redirect Chain Analyzer — Trace & Security Check (`perryay/url-redirect-chain-analyzer`) Actor Trace HTTP redirect chains for any URL. Detects redirect loops, insecure http downgrades, open redirect vulnerabilities, and tracking/analytics parameters. Supports single and batch mode (up to 50 URLs). Returns full hop-by-hop chain with security grading. - **URL**: https://apify.com/perryay/url-redirect-chain-analyzer.md - **Developed by:** [Perry AY](https://apify.com/perryay) (community) - **Categories:** Developer tools, SEO tools - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.025 / actor start This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js/docs.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python/docs.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## URL Redirect Chain Analyzer — Trace, Security & SEO Redirect Analysis Trace and analyze HTTP redirect chains for any URL. Detect redirect loops, insecure HTTP downgrades, open redirect vulnerabilities, and tracking/analytics parameters. Works with single URLs or batch mode up to 50 URLs. Built with async HTTPX for non-blocking redirect tracing. No Playwright, no browser automation. Each hop is captured manually for full visibility into the redirect chain. --- ### What does it do? URL Redirect Chain Analyzer takes one or more URLs and follows their HTTP redirect chains hop by hop (301, 302, 303, 307, 308). For each URL it produces a complete chain with status codes, response headers, security grading, and vulnerability detection. It strips tracking parameters from final URLs and assigns a security grade from A (secure) to F (critical). --- ### Features 1. **Full redirect chain tracing** — Follows every hop from initial URL to final destination, capturing status codes and headers per hop 2. **Redirect loop detection** — Identifies cyclic redirects that would cause browser timeouts 3. **Insecure downgrade detection** — Flags transitions from HTTPS to HTTP that expose traffic 4. **Open redirect vulnerability check** — Detects redirects to completely different domains or non-HTTP schemes 5. **Tracking parameter detection** — Identifies and removes 40+ known analytics/tracking parameters (UTM, Facebook, Google Ads, HubSpot, etc.) 6. **Security grading (A–F)** — Automated security score based on chain complexity, vulnerabilities, and protocol usage 7. **DNS resolution** — Resolves the final hostname to an IP address for additional context 8. **Batch mode** — Process up to 50 URLs in a single run with concurrent tracing 9. **Hop-by-hop headers** — Captures Location, Content-Type, Set-Cookie, Cache-Control, Server, X-Redirect-By, and X-Frame-Options at each step 10. **Graceful error isolation** — A failed URL never blocks the rest of the batch --- ### Why use this? | Pain Point | How This Actor Solves It | |---|---| | Manual curl/wget tracing is slow and doesn't scale | Automated batch analysis traces up to 50 URLs with concurrent requests | | SEO teams need to audit redirect chains for link equity loss | Chain length and status codes enable quick assessment of redirect health | | Security teams need to scan for open redirects | Built-in open redirect detection and security grading | | Marketing teams want clean, tracking-free URLs | Automatic detection and stripping of 40+ tracking parameters | | DevOps needs to monitor redirect chain health over time | Structured JSON output feeds dashboards and monitoring pipelines | | Developers debugging redirect logic need hop-by-hop visibility | Full per-hop capture with headers, status codes, and timing | --- ### Who is it for? | Persona | What They Use It For | |---|---| | SEO specialist | Audit redirect chains to assess link equity loss and identify broken redirects | | Security engineer | Scan for open redirect vulnerabilities that could be used in phishing attacks | | Marketing analyst | Strip tracking parameters from campaign URLs for clean analytics data | | Web developer | Debug redirect logic during site migrations or URL restructuring | | DevOps engineer | Monitor redirect chain health in CI/CD pipelines and uptime checks | | Penetration tester | Identify insecure redirect paths and protocol downgrade vulnerabilities | | Content manager | Verify that bookmarked URLs, shortened links, and redirects still work correctly | --- ### Input Parameters | Field | Type | Required | Default | Description | |---|---|---|---|---| | `mode` | string (enum) | Yes | `single` | `single` or `batch` | | `url` | string | If mode=single | — | Full URL with scheme (https://example.com/path) | | `urls` | array of strings | If mode=batch | [] | List of URLs to trace (max 50) | | `security_scan` | boolean | No | false | Enable advanced security analysis and grading | --- #### Example Input **Single mode:** ```json { "mode": "single", "url": "https://example.com/redirect-test", "security_scan": true } ```` **Batch mode:** ```json { "mode": "batch", "urls": [ "https://example.com/redirect-test", "https://example.com", "https://example.com/shortcut" ], "security_scan": true } ``` *** ### Output Format Each dataset row is one analyzed URL with the following fields: | Field | Type | Description | |---|---|---| | `input_url` | string | The original URL submitted for analysis | | `final_url` | string | Final URL after all redirects (or the original if no redirect) | | `chain_length` | integer | Number of redirect hops (0 if no redirect) | | `has_redirect` | boolean | True if at least one redirect was followed | | `is_loop` | boolean | True if a redirect loop was detected | | `is_open_redirect` | boolean | True if a potential open redirect was found | | `has_insecure_downgrade` | boolean | True if a HTTPS→HTTP downgrade occurred | | `has_tracking_params` | boolean | True if tracking/analytics parameters were found in the final URL | | `tracking_params_found` | array | List of detected tracking parameter names | | `stripped_url` | string | Final URL with tracking parameters removed | | `final_status_code` | integer | HTTP status code of the final response | | `security_grade` | string | Security grade: A (secure), B, C, D, or F (critical) | | `total_duration_ms` | number | Total time to trace the full chain in milliseconds | | `dns_resolved_to` | string | Resolved IP address of the final hostname | | `warnings` | array | List of warning messages (loops, downgrades, etc.) | | `error` | string | Error message if the analysis failed (empty on success) | | `hops` | array | Array of hop objects with step, url, status\_code, headers, and flags per redirect | Each hop object in the `hops` array contains: | Field | Type | Description | |---|---|---| | `step` | integer | Step number in the redirect chain (starting at 0) | | `url` | string | The URL at this hop | | `status_code` | integer or null | HTTP status code of the response | | `headers` | object | Response headers (Location, Content-Type, etc.) | | `is_secure` | boolean | Whether this hop used HTTPS | | `is_insecure` | boolean | Whether this hop used HTTP | | `is_loop` | boolean | True if this hop created a redirect loop | *** #### Example Output ```json { "input_url": "https://example.com/redirect-test", "final_url": "https://example.com/final", "chain_length": 2, "has_redirect": true, "is_loop": false, "is_open_redirect": false, "has_insecure_downgrade": false, "has_tracking_params": false, "tracking_params_found": [], "stripped_url": "https://example.com/final", "final_status_code": 200, "security_grade": "A", "total_duration_ms": 312.5, "dns_resolved_to": "93.184.216.34", "warnings": [], "error": "", "hops": [ { "step": 0, "url": "https://example.com/redirect-test", "status_code": 302, "headers": {"location": "/intermediate", "server": "nginx"}, "is_secure": true, "is_insecure": false, "is_loop": false }, { "step": 1, "url": "https://example.com/intermediate", "status_code": 301, "headers": {"location": "/final"}, "is_secure": true, "is_insecure": false, "is_loop": false }, { "step": 2, "url": "https://example.com/final", "status_code": 200, "headers": {"content-type": "text/html"}, "is_secure": true, "is_insecure": false, "is_loop": false } ] } ``` *** ### API Usage #### cURL ```bash curl -X POST "https://api.apify.com/v2/acts/perryay~url-redirect-chain-analyzer/runs" \ -H "Content-Type: application/json" \ -d '{ "mode": "single", "url": "https://example.com/redirect-test", "security_scan": true }' ``` #### Python (ApifyClient) ```python from apify_client import ApifyClient client = ApifyClient("YOUR_API_TOKEN") run = client.actor("perryay/url-redirect-chain-analyzer").call( run_input={ "mode": "single", "url": "https://example.com/redirect-test", "security_scan": True, } ) dataset_items = client.dataset(run["defaultDatasetId"]).list_items().items for item in dataset_items: print(f"{item['input_url']} → {item['final_url']} [Grade: {item['security_grade']}]") ``` #### Node.js ```javascript const ApifyClient = require('apify-client').ApifyClient; const client = new ApifyClient({ token: 'YOUR_API_TOKEN' }); const run = await client.actor('perryay/url-redirect-chain-analyzer').call({ mode: 'single', url: 'https://example.com/redirect-test', security_scan: true, }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach(item => console.log(`${item.input_url} → ${item.final_url} [Grade: ${item.security_grade}]`)); ``` *** ### Use Cases #### 1. SEO Redirect Audit When migrating a website or restructuring URLs, SEO teams need to verify that all old URLs properly redirect to new ones without excessive chain depths that dilute link equity. Run a batch of 50 URLs through this actor and inspect chain\_length, status codes, and final\_urls to validate the migration. #### 2. Security Vulnerability Scanning Open redirect vulnerabilities are a common finding in penetration tests. Enable security\_scan mode to automatically flag redirects that point to completely different domains or use non-standard schemes. The security grade column makes triage immediate. #### 3. Marketing Campaign URL Cleanup Marketing tools often append tracking parameters (UTM, fbclid, gclid) to URLs. Use this actor to identify tracking parameters and produce clean, stripped URLs for canonical references, analytics deduplication, or sharing. #### 4. CDN and Load Balancer Debugging Content delivery networks and load balancers often add redirect hops. Development and DevOps teams can trace URLs through these systems to verify that geo-redirects, A/B testing redirects, and protocol upgrades work correctly. #### 5. Link Shortener Analysis Trace bit.ly, tinyurl, and other shortened URLs to their final destinations. Detect if shortened links redirect through multiple services, whether they have tracking parameters appended, and whether the final destination is legitimate or potentially malicious. #### 6. Downtime Monitoring Configure a recurring Apify schedule to trace critical URLs daily. Any change in chain length, final URL, or status code triggers an investigation — helping catch misconfigured redirects before users notice. #### 7. Quality Assurance During site launches or feature deployments, QA teams can batch-test dozens of URLs to verify that redirect logic works as specified, catching bugs like missing trailing slash redirects, protocol mismatches, or unintended external redirects. #### 8. Compliance Auditing Regulatory frameworks (PCI DSS, SOC 2, ISO 27001) often require verification that sensitive endpoints don't redirect to insecure protocols. Security audit mode documents the redirect posture of critical URLs for compliance reports. *** ### FAQ #### 1. What redirect status codes are followed? 301 (Moved Permanently), 302 (Found), 303 (See Other), 307 (Temporary Redirect), and 308 (Permanent Redirect). #### 2. What is the maximum redirect depth? The actor follows up to 20 consecutive redirects before reporting an error. This is the browser-standard limit. #### 3. What tracking parameters are detected? Over 40 known parameters: UTM tags (utm\_source, utm\_medium, utm\_campaign, utm\_term, utm\_content), Facebook click IDs (fbclid), Google Click IDs (gclid, gclsrc), Microsoft Click IDs (msclkid), and many more. #### 4. How is the security grade calculated? - **A** — No issues, chain length ≤ 2, no tracking parameters, no downgrade - **B** — Minor issues (tracking parameters found, or chain length 3–5) - **C** — Warnings (chain length > 5, no other issues) - **D** — Insecure downgrade detected (HTTPS → HTTP) - **F** — Critical (open redirect or redirect loop detected) #### 5. Does this actor follow redirects in the browser? No. All redirect tracing is done server-side using HTTPX without JavaScript execution. This is intentional — it avoids the overhead of Playwright and gives deterministic results based on HTTP-level redirects only. #### 6. What happens if a URL times out? The actor has a 15-second timeout per HTTP request. If a single hop times out, the error is recorded per-URL and the actor continues processing other URLs in the batch. #### 7. Can this actor detect JavaScript-based redirects (window.location)? No. JavaScript-based redirects are not detectable server-side. This actor focuses on HTTP-level redirects (status codes 3xx). #### 8. What is the difference between single and batch mode? In single mode, you submit one URL at a time. In batch mode, you can submit up to 50 URLs in a single run, and they are processed concurrently (up to 5 at a time) for faster throughput. #### 9. How accurate is the open redirect detection? The actor flags potential open redirects when a redirect Location header points to a completely different domain or uses a non-standard scheme. This is a heuristic — false positives are possible when legitimate cross-domain redirects occur (e.g., OAuth flows). #### 10. Can I integrate this into a CI/CD pipeline? Yes. The actor can be called via the Apify API with a simple POST request. The structured JSON output integrates naturally with monitoring systems, dashboards, and alerting tools. *** ### MCP Integration Add this actor to your MCP (Model Context Protocol) server configuration: ```json { "mcpServers": { "apify-redirect-analyzer": { "command": "npx", "args": [ "-y", "@apify/mcp-server-actors", "--actors=perryay/url-redirect-chain-analyzer" ] } } } ``` *** ### Related Tools - **[Link Quality Analyzer](https://apify.com/perryay/link-quality-analyzer)** — Deep URL analysis with broken link detection and quality scoring - **[URL Health Checker](https://apify.com/perryay/url-health)** — SSL and URL health monitoring with uptime checks - **[HTTP Security Headers Analyzer](https://apify.com/perryay/http-security-headers-analyzer)** — Analyze HTTP security headers for compliance *** ### SEO Keywords URL redirect chain analyzer, redirect tracer, HTTP redirect checker, redirect loop detection, open redirect vulnerability scanner, tracking parameter stripper, UTM cleanup tool, URL security analysis, redirect audit tool, SEO redirect checker, batch URL redirect analyzer, HTTP status code checker, link shortener expander, redirect chain depth tool # Actor input Schema ## `mode` (type: `string`): Choose single URL analysis or batch processing of multiple URLs. ## `url` (type: `string`): The URL whose redirect chain you want to trace. Must include scheme (http:// or https://). ## `urls` (type: `array`): List of URLs to analyze in batch mode (max 50). Each must include scheme. ## `security_scan` (type: `boolean`): Enable advanced security checks including open redirect detection, insecure downgrade detection, and security grading (A-F). ## Actor input object example ```json { "mode": "single", "url": "https://example.com/redirect-test", "urls": [ "https://example.com/redirect-test", "https://httpbin.org/redirect/3" ], "security_scan": false } ``` # Actor output Schema ## `results` (type: `string`): Redirect chain analysis results delivered via the default dataset # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "mode": "single", "url": "https://example.com/redirect-test", "urls": [ "https://example.com/redirect-test", "https://httpbin.org/redirect/3" ] }; // Run the Actor and wait for it to finish const run = await client.actor("perryay/url-redirect-chain-analyzer").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "mode": "single", "url": "https://example.com/redirect-test", "urls": [ "https://example.com/redirect-test", "https://httpbin.org/redirect/3", ], } # Run the Actor and wait for it to finish run = client.actor("perryay/url-redirect-chain-analyzer").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "mode": "single", "url": "https://example.com/redirect-test", "urls": [ "https://example.com/redirect-test", "https://httpbin.org/redirect/3" ] }' | apify call perryay/url-redirect-chain-analyzer --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=perryay/url-redirect-chain-analyzer", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "URL Redirect Chain Analyzer — Trace & Security Check", "description": "Trace HTTP redirect chains for any URL. Detects redirect loops, insecure http downgrades, open redirect vulnerabilities, and tracking/analytics parameters. Supports single and batch mode (up to 50 URLs). Returns full hop-by-hop chain with security grading.", "version": "1.1", "x-build-id": "Kt7o9RuDPs8Wad0QM" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/perryay~url-redirect-chain-analyzer/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-perryay-url-redirect-chain-analyzer", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/perryay~url-redirect-chain-analyzer/runs": { "post": { "operationId": "runs-sync-perryay-url-redirect-chain-analyzer", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/perryay~url-redirect-chain-analyzer/run-sync": { "post": { "operationId": "run-sync-perryay-url-redirect-chain-analyzer", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "required": [ "mode" ], "properties": { "mode": { "title": "Analysis Mode", "enum": [ "single", "batch" ], "type": "string", "description": "Choose single URL analysis or batch processing of multiple URLs.", "default": "single" }, "url": { "title": "URL to Analyze", "type": "string", "description": "The URL whose redirect chain you want to trace. Must include scheme (http:// or https://).", "default": "" }, "urls": { "title": "URL List (Batch Mode)", "type": "array", "description": "List of URLs to analyze in batch mode (max 50). Each must include scheme.", "items": { "type": "string" }, "default": [] }, "security_scan": { "title": "Enable Security Analysis", "type": "boolean", "description": "Enable advanced security checks including open redirect detection, insecure downgrade detection, and security grading (A-F).", "default": false } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```