Skip to content

Commit 1b7086f

Browse files
committed
README.md update
1 parent d68f399 commit 1b7086f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ whoiswatcher was built to:
1515

1616
* Perform large sets of whois lookups quickly. It can be run in lambda or with serverless resources.
1717

18-
* Given a large set of domains as input, whoiswatcher will notify you to a domain registered to a company in your scope.
18+
* Given a large set of domains as input, whoiswatcher will alert you of a domain in your scope (e.g. registrant email)
1919
For example, if you feed it a list of yesterday's registered domains ([Daily Newly Registered Domains](https://www.whoisds.com/newly-registered-domains)) and there is a matching artifact to look for (e.g. registrant email) in your configuration; it will print to stdout.
20-
The configuration can also combine two pieces of information (see Use Cases).
20+
The configuration can also combine two pieces of information. For example a domain name (e.g. Tesla) plus the registrar they typically use (e.g. DNSination). See Use Cases below for more examples.
2121

2222
* whoiswatcher is designed to be fast, configurable, and with predictable output. For example, you can provide a single domain from stdin or a large set in a file and store searchable JSON output.
2323

@@ -37,7 +37,7 @@ echo fidelity.com | whoiswatcher
3737

3838
### Getting Alerted on an Artifact
3939

40-
First, we need to set a list of components (e.g. email, organization, phone, etc.) to watch on in `.watchlist.yaml`:
40+
First, we need to set a list of components (e.g. email, organization, phone, etc.) to watch in `.watchlist.yaml`:
4141

4242
```yaml
4343
- key: email
@@ -130,7 +130,7 @@ Combo Match: [{domain contains tesla} {organization contains DNStination}]
130130

131131
### Searching Historic Domains
132132

133-
Let's say in the past I performed a WHOIS lookups using whoiswatcher on a large set of domains and stored the results to a JSON file. Later I want to come back and search through the entries using an updated watchlist:
133+
Let's say in the past we performed a WHOIS lookups using whoiswatcher on a large set of domains and stored the results to a JSON file. Later we want to come back and search through the entries using an updated watchlist:
134134

135135
```bash
136136
./whoiswatcher -j results.json -w .newwatchlist.yaml

0 commit comments

Comments
 (0)