Privacy
Your result is processed to answer the current request
IPMora is intentionally built without application storage, user accounts, cookies, advertising technology, behavioral analytics, or lookup history.
Data processed for the result
To display the current-IP page, the application temporarily processes the public IP address and any approximate country, region, city, or time-zone values supplied by the hosting infrastructure.
IP lookup processes the address submitted in the form. Public IP comparison processes the supplied before-and-after addresses, or a supplied before address and the public IP attached to the current request.
These values are used to render the current response. IPMora does not place them in an application database and does not create a lookup or comparison history.
What IPMora does not use
- No cookies or local-storage identifiers.
- No analytics, advertising pixels, or session recording.
- No browser fingerprinting.
- No user profiles or account system.
ASN data
If the deployment has a local IPinfo Lite dataset, public-address results can include ASN and AS organization. Queried IP addresses are not sent to IPinfo. If the dataset is unavailable, IP validation and scope classification continue without ASN data.
IP address data powered by IPinfo.
Other external network services
DNS lookups are visible to the resolver used by the hosting runtime. WHOIS lookups send the domain to its authoritative public RDAP registry. Header and port checks connect directly to the submitted public target, which sees the deployment network address.
Public IP comparison uses only local validation and request data. It does not call an IP classification provider.
What stays local and what contacts others
IPMora avoids application-level tracking, but some tools must contact normal internet infrastructure to answer the request you submit.
| Tool | What stays inside IPMora | What may contact another service |
|---|---|---|
| Current IP, IP Lookup, and Public IP Comparison | Validation, comparison, request data, and local ASN dataset checks. | No external IP intelligence API is called for submitted IP addresses. |
| DNS Lookup | The submitted domain and results are not saved in an IPMora database. | The domain is resolved through the DNS resolver used by the hosting runtime. |
| WHOIS Lookup | IPMora returns selected public fields and does not keep a domain history. | The domain is sent to the IANA RDAP directory and the authoritative RDAP registry. |
| HTTP Headers | Only a focused allowlist of response headers is read. | A HEAD request is sent from the IPMora deployment network to the submitted public URL. |
| Port Checker | Only one allowlisted TCP port is checked after authorization. | One TCP connection attempt is sent from the IPMora deployment network to the public target. |
Hosting infrastructure
IPMora is designed for deployment on Vercel. Like other hosting providers, Vercel may process technical data required to route requests, maintain security, prevent abuse, operate infrastructure, and deliver the service. This application does not claim that no technical processing occurs.
Clipboard access
The Copy IP button asks your browser to copy the already displayed value when you activate it. IPMora does not read other clipboard content.
Location and comparison limitations
Displayed location is an IP-based estimate and can represent a network exit or gateway rather than a physical location. A VPN or ordinary network change can alter the visible public IP, but an address comparison alone cannot prove what caused the change.
Short-lived abuse prevention
Tool APIs apply basic request limits. The application derives an ephemeral one-way identifier from the request IP and keeps only the counter in local memory for the short rate-limit window. It is not written to a database or application log.