Hostname
salesforceiq.com
Last fetched
salesforceiq.com resolves to 104.109.10.129, announced in 104.109.10.0/24 by AKAMAI-AMS - Akamai International B.V. in BR. salesforceiq.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
- 104.109.10.129
104.109.10.0/24 · AKAMAI-AMS - Akamai International B.V. · São Paulo, BR
- 104.109.11.129
104.109.11.0/24 · AKAMAI-AMS - Akamai International B.V. · São Paulo, BR
- 18.185.24.46
18.184.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 184.25.179.132
184.25.179.0/24 · AKAMAI-AMS - Akamai International B.V. · Sydney, AU
- 184.31.10.133
184.31.10.0/24 · AKAMAI-AMS - Akamai International B.V. · Los Angeles, US
- 23.1.106.133
23.1.106.0/24 · AKAMAI-AMS - Akamai International B.V. · New York, US
- 3.126.5.188
3.124.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.71.139.153
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:292
- Registrant organisation
- salesforce.com,
- Contact emails
- registrar-updates@salesforce.com, sre@relateiq.com
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns-168.awsdns-21.com
- ns-795.awsdns-35.net
- dns1.p01.nsone.net
- dns2.p01.nsone.net
- dns3.p01.nsone.net
- dns4.p01.nsone.net
- ns-1031.awsdns-00.org
- ns-2008.awsdns-59.co.uk
MX records
- mxa-00177002.gslb.pphosted.com
- mxb-00177002.gslb.pphosted.com
SPF policy
- ip: 52.10.44.176/32
- include: amazonses.com
- include: cust-spf.exacttarget.com
- include: _spf.google.com
- include: et._spf.pardot.com
- include: stspg-customer.com
- include: mail.zendesk.com
Threat-feed evidence
History
Related pages
Pivot from salesforceiq.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: "salesforceiq.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.