Hostname
fpimx.com
Last fetched
fpimx.com resolves to 108.165.47.213, announced in 108.165.74.0/24 by CUBEPATH - CubePath in US. fpimx.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 108.165.47.213
108.165.74.0/24 · CUBEPATH - CubePath · Houston, US
- 108.165.47.214
108.165.74.0/24 · CUBEPATH - CubePath · Houston, US
- 108.165.47.219
108.165.74.0/24 · CUBEPATH - CubePath · Houston, US
- 108.165.47.220
108.165.74.0/24 · CUBEPATH - CubePath · Houston, US
- 142.171.188.162
- 142.171.188.163
- 142.171.188.164
- 142.171.188.165
- 142.171.188.166
- 148.135.108.34
- 148.135.108.35
- 148.135.108.38
- 172.234.24.211
172.236.0.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.57.117
172.240.29.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 23.80.38.217
- 23.80.38.218
- 23.80.38.219
- 51.77.51.201
- 51.77.51.204
- 51.77.51.209
Attribution
cubepath
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- david gibbons
- Contact emails
- c8dc48b8069b4e8f8ce3cca7db7dc194.protect@withheldforprivacy.com, whois@cloudmyoffice.com
Subdomains
Mail and authentication
Nameservers
- ns-37.awsdns-04.com
- dns101.registrar-servers.com
- dns102.registrar-servers.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1534.awsdns-63.org
- ns-1777.awsdns-30.co.uk
- ns-1961.awsdns-53.co.uk
MX records
- mx.fpimx.com
- mx.plingest.com
SPF policy
- a: dns.fpimx.com
Threat-feed evidence
History
Related pages
Pivot from fpimx.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "fpimx.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.