Wiki link
This commit is contained in:
Raphael
GitHub
parent
17c11ec794
commit
f0b54fbef4
89
README.md
89
README.md
|
|
@ -25,19 +25,6 @@ One of the most advanced tools to scan phone numbers using only free resources.
|
||||||
|
|
||||||
The tool only accepts E164 and International formats as input.
|
The tool only accepts E164 and International formats as input.
|
||||||
|
|
||||||
- E164: +3396360XXXX
|
|
||||||
- International: +33 9 63 60 XX XX
|
|
||||||
- National: 09 63 60 XX XX
|
|
||||||
- RFC3966: tel:+33-9-63-60-XX-XX
|
|
||||||
- Out-of-country format from US: 011 33 9 63 60 XX XX
|
|
||||||
|
|
||||||
## Available scanners
|
|
||||||
|
|
||||||
Use `any` to disable this feature. Default value: `all`
|
|
||||||
|
|
||||||
- numverify
|
|
||||||
- ovh
|
|
||||||
|
|
||||||
## Installation
|
## Installation
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
|
|
@ -48,6 +35,8 @@ python3 -m pip install -r requirements.txt
|
||||||
|
|
||||||
## Usage
|
## Usage
|
||||||
|
|
||||||
|
### [The full usage documentation has been moved to the wiki](https://github.com/sundowndev/PhoneInfoga/wiki)
|
||||||
|
|
||||||
```
|
```
|
||||||
usage: phoneinfoga.py -n <number> [options]
|
usage: phoneinfoga.py -n <number> [options]
|
||||||
|
|
||||||
|
|
@ -69,80 +58,6 @@ optional arguments:
|
||||||
-u, --update Update the tool & databases
|
-u, --update Update the tool & databases
|
||||||
```
|
```
|
||||||
|
|
||||||
Example (quotes are optional, use it when typing special formats) :
|
|
||||||
|
|
||||||
```
|
|
||||||
python3 phoneinfoga.py -n "(+42)837544833"
|
|
||||||
```
|
|
||||||
|
|
||||||
Check for a number range on OVH :
|
|
||||||
|
|
||||||
```
|
|
||||||
python3 phoneinfoga.py -n +42837544833 -s ovh
|
|
||||||
```
|
|
||||||
|
|
||||||
Check several numbers at once :
|
|
||||||
|
|
||||||
```
|
|
||||||
python3 phoneinfoga.py -i numbers.txt -o results.txt
|
|
||||||
```
|
|
||||||
|
|
||||||
**Note: `--osint` is not compatible with `--output` option.**
|
|
||||||
|
|
||||||
Use all scanners and run OSINT reconnaissance :
|
|
||||||
|
|
||||||
```
|
|
||||||
python3 phoneinfoga.py -n +42837544833 -s all --osint
|
|
||||||
```
|
|
||||||
|
|
||||||
## Formatting
|
|
||||||
|
|
||||||
E.164 formatting for phone numbers entails the following:
|
|
||||||
|
|
||||||
- A + (plus) sign
|
|
||||||
- International Country Calling code
|
|
||||||
- Local Area code
|
|
||||||
- Local Phone number
|
|
||||||
|
|
||||||
For example, here’s a US-based number in standard local formatting: (415) 555-2671
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Here’s the same phone number in E.164 formatting: +14155552671
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
In the UK, and many other countries internationally, local dialing may require the addition of a '0' in front of the subscriber number. With E.164 formatting, this '0' must usually be removed.
|
|
||||||
|
|
||||||
For example, here’s a UK-based number in standard local formatting: 020 7183 8750
|
|
||||||
|
|
||||||
Here’s the same phone number in E.164 formatting: +442071838750
|
|
||||||
|
|
||||||
## Dealing with Google captcha
|
|
||||||
|
|
||||||
PhoneInfo use a workaround to handle Google bot detection. When running OSINT scan, you will usually be blacklisted very easily by Google, which will ask the tool to complete a captcha.
|
|
||||||
|
|
||||||
>When you search on Google using custom requests (Google Dorks), you get very easily blacklisted. So Google shows up a page where you have to complete a captcha to continue. As soon as the captcha is completed, Google create a cookie named "GOOGLE_ABUSE_EXEMPTION" which is used to whitelist your browser and IP address for some minutes. This temporary whitelist is enough to let you gather a lot of information from many sources. So I decided to add a simple user manipulation to bypass this bot detection. [...] So I'll just try make requests and wait until I get a 503 error, which means I got blacklisted. Then I ask the user to follow an URL to manually complete the captcha and copy the whitelist token to paste it in the CLI. The tool is now able to continue to scan!
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### How to handle captcha
|
|
||||||
- Follow the URL
|
|
||||||
- Complete the captcha if needed
|
|
||||||
- Open the dev tool (F12 on most browsers)
|
|
||||||
- Go to **Storage**, then **Cookies**
|
|
||||||
- Copy the value of the *GOOGLE_ABUSE_EXEMPTION* cookie and simply paste it in the CLI
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Troubleshooting
|
|
||||||
|
|
||||||
The cookie should be created after you complete the captcha. If there's no captcha and *GOOGLE_ABUSE_EXEMPTION* cookie, try pressing F5 to refresh the page. The cookie should've been created. If refreshing the page does not help, change the query to something different (change the number or add text). Google will not necessarily ask you to complete a captcha if your request is the exact same as the previous one, because it'll usually be cached.
|
|
||||||
|
|
||||||
## Custom formatting
|
|
||||||
|
|
||||||
Sometimes the phone number has footprints but is used with a different formatting. This is a problem because for example if we search for "+15417543010", we'll not find web pages that write it that way : "(541) 754–3010". So the tool use a (optional) custom formatting given by the user to find further and more accurate results. To use this feature properly and make the results more valuable, try to use a format that someone of the number' country would usually use to share the phone number online. For example, French people usually write numbers that way online : *06.20.30.40.50*, *06 20 30 40 50*.
|
|
||||||
|
|
||||||
## License
|
## License
|
||||||
|
|
||||||
This tool is licensed under the GNU General Public License v3.0.
|
This tool is licensed under the GNU General Public License v3.0.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue