MyIP.dogChecking…
Privacy Policy
Understand how MyIP.dog handles connection information, network queries, maps, analytics, browser storage and third-party diagnostic services.
Last updated: 2026-09-28
Understand how MyIP.dog handles connection information, network queries, maps, analytics, browser storage and third-party diagnostic services.
Last updated: 2026-09-28
Checking…
This Privacy Policy describes the public network tools and informational pages at MyIP.dog. The service helps you see the public address used for a connection, inspect public network records, and perform selected diagnostics. The public tools do not require registration, payment, a personal profile, or an uploaded identity document. References below to a browser mean the software you use to open the website; they do not mean that every operation remains entirely on your device.
Different tools have different data flows. A subnet calculation can happen locally, while a DNS query needs a resolver and a remote connectivity test needs a measurement provider. Read the disclosure beside a tool before starting it. Our data sources and methodology explain the providers, measurements, and limitations in more detail. This Privacy Policy should be read with those explanations, especially when you are testing a network belonging to an employer or another person.
When you visit a website, the network serving it receives connection information, including a public IP address. MyIP.dog uses Cloudflare to deliver the website. On a supported Cloudflare request, the homepage uses the address observed at the edge and associated network metadata to display your result in the initial page response. Available metadata can include an estimated country, region, city, time zone, autonomous system number, network organization, and approximate coordinates.
An IP address may identify a shared gateway, VPN exit, proxy, mobile carrier, or other intermediary. It is not a verified identity or an exact home address. We do not request browser GPS permission to draw the homepage map. Missing location information stays unavailable. If the application cannot obtain a usable server observation, the browser may request an address from ipify; the displayed source identifies that fallback. That provider receives the browser connection making the request.
Personalized application responses use headers instructing browsers and intermediary caches not to store them. This helps avoid serving one visitor's result to someone else. It does not remove records maintained independently by your network provider, the hosting platform, a third-party service, or software on your device. A response header is not a promise that no infrastructure logs exist.
DNS, reverse DNS, hostname, IP registration, domain registration, and ASN tools process the address or name you submit. The application validates the input and sends the relevant query to the stated source. Depending on the tool, these sources include Google Public DNS, IANA bootstrap directories, the responsible RDAP registry, and RIPEstat. The query target is needed to obtain the result. Do not enter passwords, private access tokens, confidential internal hostnames, or personal information unrelated to the diagnostic.
Some results come from public registration data and can contain an organization's name or public contact information. Their appearance in a result does not establish that the information belongs to you, that it is current, or that you have permission to republish it. Missing registration fields do not establish that a person is anonymous. Corrections to source records generally need to be requested from the registry or data provider responsible for the record.
The subnet calculator and CIDR calculator perform their address arithmetic within the browser. They do not need to contact addresses in the calculated ranges. Their inputs and calculated results are not submitted to a calculation server by those tools. Copy buttons write only the result you choose to your system clipboard. Other applications, browser extensions, and clipboard synchronization software may be able to read clipboard contents according to their own permissions and settings.
The email header analyzer parses pasted header text in the current tab. It does not send those headers to an analysis endpoint, perform automatic address lookups, or save the input in browser storage. Editing clears the previous result, and Clear or leaving the page discards the working state. The optional copied report contains original header fields and may include names, email addresses and message identifiers; review it before sharing. Message-body content after the first blank line is excluded from the report.
The password and PIN generators use the browser's cryptographic random source after you request generation. Generated values stay in the current page's memory and are not uploaded, put in URLs, attached to analytics events or written to local/session storage. Editing settings, Clear and leaving the page discard the results; hiding the tab conceals visible values. An explicit Copy action places the original value on your system clipboard, even if it is hidden on screen. Clearing the page does not erase clipboard history or copies saved in other applications. We do not offer a password vault or recovery history for generated values.
Some tests make additional network requests when you start them. IPv4 and IPv6 checks contact address-family endpoints. The WebRTC test asks the browser to gather connection candidates using the disclosed STUN service. The speed test transfers generated payloads to and from Cloudflare endpoints, so it consumes data and exposes the test connection to that provider. It does not ask you to select personal files for upload.
Ping, traceroute and HTTP response header checks use Globalping measurement probes. HTTP checks also disclose the URL path and query, selected addresses, request settings and returned headers through public measurements. Do not submit secret links, tokens or personal information; clearing our page does not delete an upstream measurement. A submitted destination and selected test settings are sent to that service. Measurement identifiers and source links are shown with results. Treat remote measurement destinations and shared result links as information disclosed to the measurement provider; do not use them for confidential targets. A port check connects from the service runtime to a validated public destination. The destination can observe that connection even when the test sends no application payload.
The IP comparison feature makes direct browser requests to the destinations named in its results. Each destination observes its own connection. This Privacy Policy does not promise that different destinations will see the same address. VPN routing, split tunneling, protocol selection, and provider availability can change the observations. Unavailable or preview diagnostics are labeled; a missing result does not establish that a connection is private or secure.
The homepage downloads map resources from OpenFreeMap and renders them using MapLibre. The map provider receives requests for the resources needed to draw the visible area. Requested map tiles can correspond to an approximate area inferred from your network location. These are third-party requests even though the map appears within our page. The visible attribution identifies the map data contributors and resource provider.
Map failure does not prevent the primary IP result from being displayed. You can also block external resource requests through browser controls or extensions, although doing so may disable maps or particular diagnostics. Following an external source link leaves MyIP.dog and makes a new request to the linked website. External providers have their own privacy practices and retention policies.
The website loads Google Analytics to understand page usage and improve the service. Analytics requests can include the page URL, page title, referrer information, browser and device information, and identifiers managed by the analytics service. Network requests to Google also disclose connection information to Google. The application does not deliberately attach tool inputs or diagnostic result objects as custom analytics events. Avoid placing confidential information in a page URL or sharing a URL that contains it.
The browser stores your chosen color theme so that the interface can remember it. The application may also set a referral-source cookie when a URL includes a supported campaign source. That cookie lasts up to 30 days. Google Analytics may use its own cookies. You can manage cookies, clear site storage, or block analytics through your browser and related privacy tools. Clearing local storage resets preferences; blocking analytics does not prevent local subnet or CIDR calculations.
Hiding an IP or result changes its visibility on the screen. It does not alter your network address, erase an upstream request, or create a VPN. Similarly, clearing a tool's interface removes its displayed state but does not instruct independent providers to delete information they already received. Keep those distinctions in mind when recording a screen or sharing a diagnostic with support staff.
The public application does not create an account-based archive of your diagnostic history. Temporary request-limit counters and in-progress state support operation and abuse prevention. Hosting, analytics, DNS, mapping, registry, and measurement providers may retain their own operational records under their policies. We do not claim a single retention period covering those independent services. If a particular provider's retention is important to your use, review its policy before starting the associated operation.
We use HTTPS and validate supported inputs. We restrict private and special-use destinations where a tool initiates a remote request, and apply request limits to reduce abuse. These measures reduce specific risks; they do not make a browser session, third-party result, or network configuration immune to failures. Do not send secrets or rely on the website as a storage system for sensitive information.
Privacy rights and available requests depend on the applicable law and the data involved. A request concerning a public registry record or a third-party measurement may need to be directed to that source. For information about this website and its current scope, see About. The operator's direct contact details are being finalized for this launch. The date above identifies this version of the Privacy Policy; material changes will be reflected in the published policy and its update date.