PRIVACY

What GlobeProxy processes and keeps

Last updated October 30, 2026

This page describes how the site works today, tool by tool. It is a plain-language description, not a contract or a legal guarantee, and it will be updated if the site changes.

In short

  • No account, no sign-up, no forms that collect your email.
  • No cookies are set by this site, and nothing is stored in your browser.
  • No analytics, advertising or tracking scripts. Fonts are served from this site.
  • Results are not saved to a database. The few things we keep are listed below.

What each tool processes

Full Border Check

The Full Border Check runs the same checks as the individual tools, all at once: your IP and its location and provider (from our local database), the WebRTC test, the DNS test and the headers test. The same third-party contact applies as for the WebRTC test: your browser contacts Google and Cloudflare STUN servers. The passport image and the result summary are generated in your browser. They are not sent to our server or stored, and we do not create share links. If you download or share the image, what it shows is up to you; by default it hides most of your IP address and your city. The datacenter flag and the time zone comparison are worked out from the same local database and your browser's time zone, and are not recorded.

VPN detector

The address you check (yours by default, or one you type) is sent to our server. It is compared with the local location and network database, with a list of hosting and VPN networks and with a copy of the Tor Project's public exit list that our server downloads every hour. The server also asks DNS for the address's reverse DNS name, using the server's own resolver, which forwards the question to the DNS servers our hosting provider and public resolvers operate. The result is not stored. The Full Border Check uses the same network comparison for its network stamp.

IP blacklist check

The IPv4 address you check is sent to our server, which asks seven public spam blocklists whether they list it: Spamhaus, SpamCop, Barracuda, PSBL, UCEPROTECT, DroneBL and s5h.net. This means the address is sent to those operators as part of a DNS query, through our server's resolver, and they may see it in their logs. Results are cached in the memory of the running application for one hour, keyed by the address, so a repeat check shows the same answer. The cache is not written to disk and is lost on restart. The check is limited to 10 per minute and 50 per day for each visitor address.

DNS lookup

The domain name or IP address you enter, and the record type, are sent to our server, which sends the question to the public resolvers 1.1.1.1 (Cloudflare) and 8.8.8.8 (Google). Those operators receive the name or address you looked up, coming from our server's address rather than yours. Results are not stored.

Port checker

When you run a check, our server connects back to your own IP address, the one it sees when you connect to us, on the ports you choose, and records only whether each connection succeeded, was refused or timed out. The tool never accepts any other address. The ports you picked and the results are shown to you and are not stored. Only a count of recent requests per address is kept in the memory of the running application, to enforce the limit of 5 checks a minute and 30 a day, and it is lost on restart. If you use a VPN or proxy, the address tested is the VPN or proxy's.

IPv6 test

Your browser asks three names on this site (ipv4.globeproxy.com, ipv6.globeproxy.com and ds.globeproxy.com) to return the IP address the request came from. The answer is shown to you and the score is worked out in your browser. The answers are not stored, and no cookies are used.

Browser fingerprint test

The fingerprint test is computed in your browser. The details it reads, the hashes it makes and the fingerprint ID are not sent to our server and are not stored in cookies or browser storage. The page makes no network request that contains them.

User agent parser and subnet calculator

Both run in your browser. The user agent you paste and the subnet you enter are not sent anywhere.

What's my IP

Your public IP address is read from the connection to our server and shown back to you. The location and provider come from a database stored on our own server (see DB-IP below), so your address is not sent to another company to be looked up.

IP lookup

The address you type is sent to our server and looked up in the same local database. Because the address is part of the request, it appears in our standard web server log (see Server logs).

WebRTC leak test

When you press the button, your browser contacts a Google STUN server (stun.l.google.com) and a Cloudflare STUN server (stun.cloudflare.com). They see your IP address, as any website would. The comparison is done in your browser. Our server only sees the normal requests for your IP and for the location of any addresses found. This is the only part of the site where your own browser contacts a third party. Some tools ask other services from our server instead, as described below.

DNS leak test

Your browser looks up six random names under dnstest.globeproxy.com. Our own DNS server records the address of each resolver that asks, together with the random test code, and keeps them in memory for ten minutes. They are then deleted. They are not written to disk. The resolver addresses are looked up in the local location database so the page can show who runs them.

Proxy checker

The proxy address, type and optional username and password are sent to our server in a request body and used for one test connection. Credentials are never stored or logged. The test makes a request through your proxy to a page on this site, so that request appears in our server log with the proxy's exit IP address. The proxy itself will see a connection from our server.

HTTP headers

Our server reads the headers of a background request from your browser and returns them to the page. They are not stored. Cookie values are never returned, only the fact that a cookie was sent.

Rate limiting

To prevent abuse, the lookup, DNS, VPN detector, blacklist check, DNS lookup and proxy-check endpoints count requests per IP address. These counts are kept in the memory of the running application only. They are not written to disk and are lost when the application restarts.

Server logs

Our web server (nginx) keeps standard access logs. Each line contains your IP address, the date and time, the page or address requested including any query string, the response code, the size of the response, the referring page and your browser's user-agent text. Logs are used to keep the site running and to investigate abuse. They are rotated daily and the 14 most recent rotated files are kept (compressed), so entries are removed after roughly two weeks. Proxy credentials sent to the proxy checker are not part of the logged request line.

Cookies and analytics

This site sets no cookies and does not use localStorage or sessionStorage. It has no analytics, advertising or tracking scripts, and we do not use third-party services to measure visits. We have no advertising on the site. We have a few labelled affiliate links to Webshare and DeleteMe (see the affiliate disclosure). If you click one, you go to that company's website (DeleteMe links pass through an affiliate tracking network first), which may set its own cookies under its own policy; this site still sets none.

IP location data

IP geolocation by DB-IP. The DB-IP Lite databases are licensed under Creative Commons Attribution 4.0 (CC BY 4.0). Locations are approximate.

Contact

There is no public contact address on this site yet. This page will list one when there is.