Hostname
planbook.com
Last fetched
planbook.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in ZA. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
planbook.com resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 3.161.94.129 | 3.161.88.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | ZA |
| 3.161.94.32 | 3.161.88.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | ZA |
| 3.161.94.7 | 3.161.88.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | ZA |
| 3.161.94.84 | 3.161.88.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | ZA |
| 3.175.227.12 | 3.175.224.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 3.175.227.28 | 3.175.224.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 3.175.227.70 | 3.175.224.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 3.175.227.95 | 3.175.224.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
WHOIS identity
- Registrar
- iana:146
- Organization
- domains by proxy,
- Contact emails
Subdomains
43 observed subdomains of planbook.com.
Showing 25 of 43. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from planbook.com in the public web crawl.
300 sites link to this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
SPF policy
2 SPF mechanisms authorising senders for planbook.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 44552839.spf06.hubspotemail.net |
| SPF_INCLUDE | _spf.google.com |
Related pages
Pivot deeper into the graph from planbook.com.
- IP · 3.161.94.129
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:146
- Country · ZA
- Email · support@planbook.com
- TLD · .com
- Browse hostnames · pl…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "planbook.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.