FAQ

General Questions

What is Vanadum?

Vanadum is a local HTTP proxy server that provides advanced TLS fingerprint emulation. It makes your HTTP requests appear as if they come from real browsers, bypassing bot detection systems.

How does it work?

Vanadum runs on http://127.0.0.1:8000
Send requests to Vanadum with target URL in headers
Vanadum makes the request with browser-like fingerprints
Response is returned to your application

What can it bypass?

TLS fingerprinting (JA3/JA4)
HTTP/2 fingerprinting
Browser detection
Anti-bot systems like Cloudflare, Akamai, PerimeterX

Do I need to modify my code?

Minimal changes - just point your HTTP client to Vanadum’s localhost address and add headers for target URL and profile selection.

Browser Profiles

What profiles are available?

Available profile categories:

Chrome: Multiple versions
Safari: iOS, macOS, iPad variants
Firefox: Including Private and Android
Edge: Multiple versions
Opera: Multiple versions
OkHttp: Multiple versions
HTTP/1.1 Only: Forces HTTP/1.1 for problematic servers
Custom: Dynamic fingerprint with randomized parameters

How do I choose a profile?

Use the X-Profile header with comma-separated values:

X-Profile: chrome,firefox

Vanadum randomly selects from the specified profiles for each request.

Can I customize profiles?

Use the “Custom” profile for dynamic fingerprint generation with randomized parameters.

Which profile has the best success rate?

Chrome generally has the highest success rate as it’s the most common browser. Safari works well for iOS-targeted sites. Use multiple profiles for automatic rotation.

API Usage

What headers are required?

Required:

X-Url: Target URL to fetch

Optional:

X-Profile: Browser profile (default: chrome)
X-Proxy: Proxy server to use

How do I use proxies?

Add the X-Proxy header:

X-Proxy: socks5://user:[email protected]:1080

What HTTP methods are supported?

All standard methods:

GET, POST, PUT, DELETE, PATCH
HEAD, OPTIONS

How do I send POST data?

Send POST data in the request body as normal. Vanadum forwards it with the correct content-type.

Can I set custom headers?

Yes, include any headers in your request. Vanadum forwards them while adding browser fingerprint headers.

Performance

How many concurrent requests can it handle?

Depends on your system resources and network capacity.

Why are requests slow?

Proxy latency: External proxies add delay
Target server: Site response time varies
Connection setup: TLS handshake takes time
Rate limiting: Target site may throttle

Does it support connection pooling?

Yes, Vanadum maintains connection pools for improved performance with repeated requests to the same host.

What timeout should I use?

Recommended timeouts:

Direct connection: 10-15 seconds
With proxies: 20-30 seconds

Troubleshooting

“Connection refused” error

Verify Vanadum is running
Check it’s on port 8000
Ensure localhost is accessible
Restart Vanadum if needed

Requests still getting blocked

Try different browser profile
Use residential proxies
Add delays between requests
Check for JavaScript challenges

“Invalid X-Url” error

URL must be complete (include https://)
URL must be properly encoded
Check for invalid characters

Timeout errors

Increase timeout setting
Check proxy connectivity
Verify target site is accessible
Reduce concurrent requests

SSL/TLS errors

Target site may have certificate issues
Try different profile
Check system time/date
Update system certificates

Integration

Python example

import requests

response = requests.get(
    "http://127.0.0.1:8000/",
    headers={
        "X-Url": "https://example.com",
        "X-Profile": "chrome"
    }
)

Node.js example

const response = await fetch('http://127.0.0.1:8000/', {
  headers: {
    'X-Url': 'https://example.com',
    'X-Profile': 'chrome',
  },
});

cURL example

curl -X GET "http://localhost:8000/" \
     -H "X-Url: https://example.com" \
     -H "X-Profile: chrome"

Local traffic to Vanadum: Not encrypted (localhost)
Vanadum to target: Encrypted (TLS)
Proxy connections: Depends on proxy protocol

Can I use it for sensitive data?

Yes, but understand:

Local traffic is unencrypted
Target site receives browser-like TLS
Use SOCKS5 for end-to-end encryption with proxies

Rotate profiles periodically
Use residential proxies
Add random delays
Mimic human behavior patterns
Don’t hammer endpoints

Optimal configuration

Use connection pooling for same-host requests
Set appropriate timeouts
Match profile to target audience
Test with small batches first

When to use different profiles

Chrome: Default, works for most sites
Safari: iOS/Mac-targeted sites
Firefox: Privacy-focused sites
Edge: Microsoft services
OkHttp: Mobile app APIs

Quantium Documentation