Hostname
pepperdine.thankview.com
Last fetched
pepperdine.thankview.com resolves to 12 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
pepperdine.thankview.com resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 100.48.127.99 | 100.48.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 100.50.156.194 | 100.48.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 18.215.210.194 | 18.208.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 18.233.25.15 | 18.232.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.211.190.97 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.215.2.206 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.227.182.114 | 3.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.203.63.181 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.21.80.21 | 52.20.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.71.44.174 | 52.70.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.81.219.108 | 54.80.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 98.95.242.32 | 98.88.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
No WHOIS records are currently associated with pepperdine.thankview.com in WhisperGraph.
Web-graph footprint
Distinct hostnames that link to or from pepperdine.thankview.com in the public web crawl.
14 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
5 SPF mechanisms authorising senders for pepperdine.thankview.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | eu.mailgun.org |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | servers.mcsv.net |
| SPF_INCLUDE | spf.mtasv.net |
Related pages
Pivot deeper into the graph from pepperdine.thankview.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "pepperdine.thankview.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.