That big string is Netflix' SPF record. It's an email thing and tells the world what servers it should expect netflix.com email from.
Finding all of a website's IP addresses can be a pretty tough thing in the general case. One answer that's often enough is to just trust whatever the DNS server is giving you as the A record for that domain at the time:
% dig netflix.com
netflix.com. 74 IN A 69.53.236.17
Some websites will have several records, and will let you know those up front:
% dig google.com
google.com. 205 IN A 173.194.33.103
google.com. 205 IN A 173.194.33.110
google.com. 205 IN A 173.194.33.96
google.com. 205 IN A 173.194.33.105
google.com. 205 IN A 173.194.33.100
google.com. 205 IN A 173.194.33.97
google.com. 205 IN A 173.194.33.99
google.com. 205 IN A 173.194.33.102
google.com. 205 IN A 173.194.33.98
google.com. 205 IN A 173.194.33.104
google.com. 205 IN A 173.194.33.101
Depending on the site, things can get tricky in a hurry. Many sites, especially larger ones, will give you a different set of records at different times (or for each time you ask):
% dig indeed.com
indeed.com. 19 IN A 50.97.195.27
% dig indeed.com
indeed.com. 30 IN A 50.97.35.152
And some will give you a different address depending on which part of the world you're in. Like wordpress.com from India:
Seattle WA, United States: 192.0.78.9, 192.0.78.17
Montreal QC, Canada: 192.0.78.9, 192.0.78.17
Paris, France: 192.0.78.9, 192.0.78.17
St. Petersburg, Russia: 192.0.78.9, 192.0.78.17
Beijing, China: 192.0.78.9, 192.0.78.17
Mumbai, India: 203.90.66.98
Some sites will even mix and match those types of responses.
IPv6 throws a wrench into this, as does HTTP redirection.
Probably the thing to start with when considering which answer is best for you: what are you trying to accomplish with this information?