Hostname
cplus.touch-line.com
Last fetched
cplus.touch-line.com resolves to 52.85.78.102, announced in 52.85.72.0/21 by AMAZON-02 - Amazon.com, Inc. in US. cplus.touch-line.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
- 52.85.78.102
52.85.72.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 52.85.78.50
52.85.72.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 52.85.78.60
52.85.72.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 52.85.78.65
52.85.72.0/21 · AMAZON-02 - Amazon.com, Inc. · Miami, US
- 99.84.160.103
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 99.84.160.106
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 99.84.160.14
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 99.84.160.45
99.84.160.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
IPv6 resolution
No AAAA record for cplus.touch-line.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for cplus.touch-line.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
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-86.awsdns-10.com
- ns-681.awsdns-21.net
- 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-1255.awsdns-28.org
- ns-1945.awsdns-51.co.uk
Threat-feed evidence
History
Related pages
Pivot from cplus.touch-line.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: "cplus.touch-line.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.