Contact Check My IP
Contact the Check My IP editorial desk about factual corrections, broken tools, accessibility barriers, security reports, or ordinary product questions.
Where to write
Email [email protected] for editorial corrections, accessibility problems, and ordinary product questions. Security reports can go to [email protected]. We do not offer emergency response, subscriber identification, or legal disclosure services.
What makes a report useful
Include the page address, the time of the check, what you expected, and what appeared. Redact private addresses, tokens, account details, and message content. If a location estimate is wrong, name the database provider shown in the result when available.
Corrections
Confirmed factual errors are corrected in place. A meaningful editorial change updates the visible review date; typography and layout edits do not.
How to send a report that can be reproduced safely
The contact route is for factual corrections, broken behavior, accessibility barriers, security reports, and ordinary product questions. A useful report identifies the exact page and observable problem without exposing credentials, private conversations, or internal network data. The editorial and security addresses have different purposes, and neither address is an emergency service, a provider abuse desk, or a channel for identifying the subscriber behind an IP.
Describe the smallest reproducible issue
Include the page URL, approximate time with timezone, device or browser family when relevant, the submitted value after safe redaction, what appeared, and what you expected. Explain whether the problem repeats and whether it changes on another network or browser. A concise sequence is more actionable than a full screen recording of unrelated activity. For an IP-location disagreement, include the provider label shown if available, but do not send a home address as purported proof. For DNS or TLS behavior, name the public hostname and observation time.
Redact before sending
Never send a password, access token, recovery code, private key, session cookie, or confidential message. Raw email headers can contain personal addresses, subject information, internal hostnames, and routing details; reduce them to the specific lines needed to demonstrate the parsing problem. Screenshots can expose open tabs, bookmarks, account names, notifications, and local addresses. Crop or cover those details. If a minimal synthetic example can reproduce a formatting or accessibility bug, prefer it to production data.
Route security reports responsibly
Send a suspected vulnerability in this site to the security address with the affected endpoint, impact, and safe reproduction steps. Do not retrieve other people’s information, degrade availability, evade controls, or broaden testing beyond what is needed to describe the issue. The inbox cannot coordinate incidents on unrelated networks and cannot access ISP subscriber records. Active danger, fraud, abuse, or unlawful content should be reported to the relevant platform, network operator, qualified organizational response team, local authority, or emergency service as appropriate.
What happens to editorial corrections
A correction report is checked against the page’s actual claim, the implementation when relevant, and an authoritative source. Confirmed errors are updated at the existing URL. A visible review date changes after meaningful factual or instructional work, not after punctuation or layout changes. A disagreement with an approximate external dataset may require clarification of the page language or a report to that provider rather than replacement with an unverified location. The editorial policy describes source selection, originality, commercial boundaries, and the decision to consolidate overlapping topics.
A practical reading sequence
| Starting point | Reasonable use | Important boundary |
|---|---|---|
| Editorial correction | [email protected] | Claim, source, page URL |
| Accessibility problem | [email protected] | Interaction, browser, assistive context |
| Site security issue | [email protected] | Endpoint, impact, safe reproduction |
For a broken link, identify both the Check My IP page and the linked source title. For a structured-data or search-display concern, include the testing tool and exact warning rather than a copied summary from an unrelated URL. For a performance report, note whether the issue concerns initial loading, interaction, or movement of the layout, and include the connection and device class. These distinctions route a report to content, application, accessibility, or infrastructure review without collecting unnecessary personal detail.
Replies cannot confirm that an address belongs to a named person, change a third-party geolocation database directly, recover an account, or compel a provider to release records. Those requests require the organization that controls the relevant data and, in some cases, formal legal process. The desk can explain what this application observed, correct its own factual statements, repair its own tools, and clarify where an external label originated. Setting that expectation protects both the reporter and the integrity of the result.
Include a reply address you control and avoid copying unrelated recipients. If follow-up requires additional evidence, continue to minimize it and use a synthetic example where possible. The aim is to establish the site defect or factual issue, not to collect a dossier about the person reporting it. Ordinary messages should receive the same privacy-aware handling as the diagnostic pages encourage.