Hostname
lpga.com
Last fetched
lpga.com resolves to 11 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
lpga.com resolves to 11 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 34.193.233.251 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.234.160.134 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.193.138.50 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.217.12.104 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 50.16.116.4 | 50.16.0.0/16 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.146.178.224 | 54.144.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.164.235.13 | 54.164.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.205.162.152 | 54.204.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.209.167.73 | 54.208.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 32.193.91.45 | 32.192.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 100.51.238.55 | 100.48.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
WHOIS data is temporarily unavailable. Refresh in a moment to retry.
Subdomains
Subdomain count is temporarily unavailable. Refresh in a moment to retry.
Web-graph footprint
Distinct hostnames that link to or from lpga.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
8 SPF mechanisms authorising senders for lpga.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | email.prnewswire.com |
| SPF_INCLUDE | mmsend.com |
| SPF_INCLUDE | netblocks.lpga.com |
| SPF_INCLUDE | outboundmail.blackbaud.net |
| SPF_INCLUDE | spf.exclaimer.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | us._netblocks.mimecast.com |
Related pages
Pivot deeper into the graph from lpga.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "lpga.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.