Skip to main content

IP Address Spoofing

FkNeo’s IP spoofing feature allows you to change your apparent IP address before starting a test, enabling you to bypass location-based restrictions and access tests from anywhere.

What is IP Spoofing?

IP spoofing is the process of making your network connection appear to originate from a different IP address than your actual one. This is useful when:
  • Tests are restricted to specific geographic locations
  • Your actual IP address is blocked or flagged
  • You need to appear as if connecting from a different network
  • Platform has IP-based access controls
IP spoofing must be configured before starting the test. It cannot be changed mid-test.

How It Works

FkNeo’s IP spoofing operates through:
  1. Browser API Manipulation - Modifies network information APIs
  2. Header Spoofing - Alters HTTP headers that contain IP information
  3. WebRTC Blocking - Prevents IP address leakage through WebRTC
  4. Geolocation Override - Provides false location data to the platform

Technical Implementation

The extension intercepts and modifies:
  • X-Forwarded-For headers
  • X-Real-IP headers
  • navigator.connection properties
  • WebRTC IP address enumeration
  • DNS leak prevention mechanisms

Using IP Spoofing

Setting Custom IP Address

To configure a custom IP address:
1

Open Test Page

Navigate to the test login or start page (do not start the test yet)
2

Activate IP Spoofing

Press Shift + P to open the IP spoofing dialog
3

Enter IP Address

Input your desired IP address in the format: xxx.xxx.xxx.xxx
4

Confirm and Start Test

Click confirm and then start your test normally

Keyboard Shortcut

ShortcutFunctionWhen to Use
Shift + PSet custom IPBefore starting test
You must set the IP address before starting the test. Setting it after the test has begun will not work.

Choosing an IP Address

IP Address Format

IP addresses must be in IPv4 format:
192.168.1.1
10.0.0.5
172.16.254.1

Selecting the Right IP

Consider these factors when choosing an IP: Public vs Private IPs
  • Public IPs (e.g., 8.8.8.8, 1.1.1.1) - Appear as internet-facing addresses
  • Private IPs (e.g., 192.168.x.x, 10.x.x.x) - Appear as local network addresses
Geographic Considerations
  • Research IP ranges for your target location
  • Use IP geolocation databases to verify IP locations
  • Ensure the IP matches expected geographic restrictions
If you’re unsure what IP to use, try finding the IP range of your institution’s network and use an address within that range.

IP Address Validation

FkNeo validates your IP address to ensure:
  • Correct format (four octets separated by periods)
  • Each octet is between 0-255
  • No invalid characters or spacing

Use Cases

Location-Based Access

Some tests are restricted to specific locations:
  • Campus-only tests requiring university network IPs
  • Regional tests limited to certain countries
  • Corporate tests requiring company network access
Solution: Set your IP to match the required location’s IP range

Blocked IP Addresses

Your actual IP might be blocked due to:
  • Previous test violations
  • Network flagging or blacklisting
  • Suspicious activity from your IP range
Solution: Use a different, clean IP address from an allowed range

Multiple Test Sessions

Taking multiple tests from the same IP might trigger alerts:
  • Platform limits on sessions per IP
  • Concurrent test restrictions
  • Anti-cheating IP monitoring
Solution: Use different IP addresses for different test sessions

Best Practices

Before Spoofing

1

Research Requirements

Understand what IP ranges are allowed for your test
2

Test the IP

Verify the IP address is not already blacklisted
3

Document the IP

Keep a record of which IP you used for each test

During Configuration

  • Double-check the IP address before confirming
  • Ensure you’re on the test page but haven’t started yet
  • Clear browser cache if switching IPs between tests

Security Considerations

IP spoofing changes how you appear to the test platform but doesn’t provide true anonymity. Your actual IP is still visible at the network level.
  • Don’t use IPs that could be traced back to prohibited locations
  • Avoid using obviously fake or invalid IP ranges
  • Consider using IPs consistent with your claimed location

Troubleshooting

IP Spoofing Not Working

Symptom: Platform still detects your real IP Solutions:
  • Ensure you set the IP before starting the test
  • Check if WebRTC is leaking your real IP
  • Verify the extension is fully enabled with Alt + R
  • Clear cookies and cache before retrying

Invalid IP Address Error

Symptom: Extension rejects your IP address Solutions:
  • Verify format is xxx.xxx.xxx.xxx
  • Check each octet is between 0-255
  • Remove any spaces or extra characters
  • Try a different, valid IP address

Test Won’t Start After Setting IP

Symptom: Test page freezes or won’t load after IP configuration Solutions:
  • Reload the page with Ctrl + R (not Alt + R)
  • Try a different IP address
  • Disable and re-enable the extension
  • Clear browser cache and cookies

IP Address Shows as Different

Symptom: Platform detects a different IP than what you set Solutions:
  • Check if you’re behind a VPN or proxy (disable them)
  • Ensure no other extensions are modifying network settings
  • Verify WebRTC leak protection is active

Technical Limitations

What IP Spoofing Can’t Do

FkNeo’s IP spoofing operates at the browser level, not the network level.
Limitations include:
  • Network-level detection - ISP and network administrators can still see your real IP
  • VPN detection - Advanced systems may detect spoofing attempts
  • Server logs - Backend servers may log your actual connection IP
  • Deep packet inspection - Network analysis can reveal true source

Complementary Technologies

For enhanced IP privacy, consider combining FkNeo with:
  • VPN services - Encrypt and route traffic through different locations
  • Proxy servers - Route requests through intermediate servers
  • Tor network - Anonymous routing (may be too slow for tests)

Advanced Configuration

WebRTC Leak Prevention

FkNeo automatically blocks WebRTC IP leaks, but you can verify:
  1. Visit a WebRTC leak test site before starting your test
  2. Confirm your real IP is not exposed
  3. Proceed with your test if leak protection is confirmed

Multiple IP Profiles

For users taking multiple tests:
  • Keep a list of different IPs for different test platforms
  • Use geographically appropriate IPs for each test
  • Rotate IPs to avoid pattern detection
Combine IP spoofing with other bypass features:

Verification

To verify your IP spoofing is working:
  1. Set your desired IP using Shift + P
  2. Check the test platform’s detected IP (if displayed)
  3. Confirm it matches your configured IP
  4. Proceed with confidence
Some test platforms display the detected IP address on the login or information page. Use this to verify your spoofing is working before starting the test.

Build docs developers (and LLMs) love