Report a bug
Describe the page, browser and steps that produced the problem. Do not include real phone numbers, account credentials or customer data.
Project contact
Contact GetPhoneNum
The GetPhoneNum Editorial Team reviews bug reports, data corrections, feature requests and questions through the public project tracker.
Suggest a correction
Include the affected country or guide, the current text and an official numbering-plan or standards source that supports the correction.
Privacy or responsible use
The issue tracker is public. Never post personal phone numbers or other sensitive information. For a sensitive report, open a minimal issue asking the maintainer to arrange a private follow-up channel.
Review the privacy policy and responsible-use policy before submitting a report.
What to expect
GetPhoneNum is an independently maintained project, not a telecommunications provider. Reports are reviewed periodically, and no response-time guarantee is offered. The project cannot identify a subscriber, confirm number ownership or provide access to calls, SMS or verification codes.
What makes a useful report
A good report gives enough context to reproduce the issue without exposing anyone's private information. For a tool bug, include the page URL, selected country, browser, the action you took and the result you expected. If the report concerns generated output, describe the pattern rather than posting a real phone number. Screenshots are helpful when they show layout or copy problems, but crop out account details before attaching them to a public issue.
For content or data corrections, the most useful evidence is an official source: a national regulator, numbering administrator, ITU document or standards page. Directory listings, unsourced blog posts and carrier marketing pages may be useful hints, but they are not enough to change a fixture contract on their own. Please include the affected country, current wording, proposed wording and a short explanation of why the source applies.
Data corrections
When a national length, trunk-prefix rule or source link appears stale, open a correction issue and cite the page that changed. The dataset, country guide, sitemap and tests may need to be updated together so users do not see conflicting examples.
Privacy questions
If a report could include personal phone numbers, customer records or security details, do not paste them into GitHub. Open a minimal issue that describes the category of problem and asks for a safer follow-up channel.
Advertising feedback
If an advertisement appears misleading, disruptive or too close to a tool control, report the page and placement. The site should keep tools usable and keep advertising clearly separated from generated phone data.
Why the contact process is public first
Most corrections are about reproducible page behavior or public numbering sources, so a public tracker lets other users see what changed and why. Sensitive material is the exception. When privacy or security details are involved, share only the minimum public description needed to start a safer review path. Public history also helps future users understand whether a reported numbering change has already been reviewed, accepted or rejected.