Last updated: October 19, 2026
Publisher and author model
MyIPScan is owned and operated by Katia Belokon, who writes and edits its guides and methodology pages and is responsible for what the site publishes. “MyIPScan Editorial Team” is the name used for that editorial process.
Katia Belokon writes and edits practical guides on IP addresses, browser privacy, VPN leaks, DNS, WebRTC, IPv6 and online privacy for MyIPScan. Articles follow the MyIPScan editorial checklist for clarity, factual accuracy and safety.
Research process
- We check tool copy against the current HTML, JavaScript, Worker, and Pages Function behavior in the repository.
- We prefer observable browser, network, and API behavior over marketing claims.
- We avoid definitive privacy claims when the signal is approximate, incomplete, or browser-dependent.
- We cite methodology pages or public documentation when a claim needs extra context.
AI assistance
AI tools may assist with outlines, drafting, summarization, editing, and checklists. AI-assisted text must still be reviewed before publication, and AI assistance does not justify unsupported credentials, fake tests, or invented results.
How the data pages are built
The IP range, VPN fact, VPN audit, VPN ownership and router pages are data pages. Their tables are generated by scripts from published sources: providers' own IP feeds and documentation, regional internet registry data, CISA's Known Exploited Vulnerabilities catalog, and vendor security advisories and end-of-life lists. Candidate facts for the VPN pages are gathered with AI assistance; a fact is published only when a script finds its quoted wording on the cited source page, and a weekly check re-reads every cited source and flags any that changed. The date on these pages is when the data was last refreshed, not a claim that anyone re-tested the provider or device.
Human review
Pages should be checked for clarity, factual accuracy, safety, broken links, unsupported claims, and consistency with the current tool implementation before publication.
No fake testing claims
MyIPScan should not make unsupported credential, lab, hands-on test-count, or verification claims unless there is a clear public basis for that claim.
Affiliate and editorial separation
Affiliate links, advertising, or partner relationships must not change tool results, exposure estimates, methodology conclusions, rankings, or safety limits. Monetized pages should link to How We Make Money or the Affiliate Disclosure where relevant.
Corrections policy
If a page is wrong, unclear, outdated, or missing a limitation, send the URL and the specific issue to hello@myipscan.net. Corrections should be prioritized when they affect user safety, privacy expectations, legal understanding, or tool interpretation.
Update policy
Content should be reviewed when browsers change WebRTC behavior, VPN providers change leak protection, DNS behavior changes, APIs change, monetization changes, or legal/privacy disclosures need updates.