Can't connect to PayPal.com with 1.1.1.1 DNS

Hi,

What happens:
When I try to open PayPal on my browser (latest Chrome, latest Firefox) with the 1.1.1.1 (and it’s IPv6 version, too) DNS server it says that

This site can’t be reached

ERR_CONNECTION_RESET

What is strange that if I make an nslookup paypal.com with the Windows’ command tool, I get the correct IP address for PayPal.

Non-authoritative answer:
Name:    paypal com
Addresses:  64.4.250.37
          64.4.250.36

If I put this IP address to my browser I can reach PayPal homepage (and after that I can open PayPal.com with domain, too).

What could be the problem?

Best regards,
Gergo

1 Like

I have a 1.1.1.1/help Connection information
https://1.1.1.1/help#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJObyIsImlzRG9oIjoiTm8iLCJyZXNvbHZlcklwLTEuMS4xLjEiOiJZZXMiLCJyZXNvbHZlcklwLTEuMC4wLjEiOiJZZXMiLCJyZXNvbHZlcklwLTI2MDY6NDcwMDo0NzAwOjoxMTExIjoiWWVzIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTAwMSI6IlllcyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IkJVRCIsImlzcE5hbWUiOiJDbG91ZGZsYXJlIiwiaXNwQXNuIjoiMTMzMzUifQ==

p.s. Sorry for the links, I can add only two links to my post.

Can you also run a ping paypal.com? Whats the output?

Can you try to load the page while you have your browser developer tools open on the network tab and post a screenshot?

Yes, of course.

C:\Users\work>ping paypal.com

Pinging paypal.com [64.4.250.37] with 32 bytes of data:
Reply from 64.4.250.37: bytes=32 time=41ms TTL=51
Reply from 64.4.250.37: bytes=32 time=37ms TTL=51
Reply from 64.4.250.37: bytes=32 time=40ms TTL=51
Reply from 64.4.250.37: bytes=32 time=38ms TTL=51

Ping statistics for 64.4.250.37:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 41ms, Average = 39ms

Sorry, my bad. ping paypal.com and ping www.paypal.com of course.

As for the screenshot, can you click the first entry and post a screenshot with the details.

Seems the DNS resolution works fine. Now the question is whether the browser resolves it to the right IP address too.

Edited the ping’s result.

The Preview and Response tabs are empty.

After removed the 1.1.1.1 DNS from the Control Panel Network section (Obtain DNS server automatically…) and run an ipconfig /flushdns the site opens without any loading time.

Could you also run

nslookup paypal.com 1.1.1.1
nslookup www.paypal.com 1.1.1.1
nslookup paypal.com 1.0.0.1
nslookup www.paypal.com 1.0.0.1

Yes. The nslookup can find the IP address from the domain.

C:\Users\work>nslookup paypal.com 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    paypal.com
Addresses:  64.4.250.36
          64.4.250.37


C:\Users\work>nslookup www.paypal.com 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    e16973.a.akamaiedge.net
Address:  2.18.70.88
Aliases:  www.paypal.com
          www.glb.paypal.com
          www.paypal.com.edgekey.net


C:\Users\work>nslookup paypal.com 1.0.0.1
Server:  one.one.one.one
Address:  1.0.0.1

Non-authoritative answer:
Name:    paypal.com
Addresses:  64.4.250.37
          64.4.250.36


C:\Users\work>nslookup www.paypal.com 1.0.0.1
Server:  one.one.one.one
Address:  1.0.0.1

Non-authoritative answer:
Name:    e16973.a.akamaiedge.net
Address:  2.18.70.88
Aliases:  www.paypal.com
          www.glb.paypal.com
          www.paypal.com.edgekey.net

Oh, I found what is wrong.

You have to open www.paypal.com instead paypal.com. But why?

So only the 2.18.70.88 address works for you, but not the 64 ones?

Exactly.

But you said it works if you enter that address manually.

3 posts were merged into an existing topic: Spam posts

Yes. As you can see the picture, if I wrote www.paypal.com the page loads, but with only paypal.com it won’t.

1 Like

But you referred to the 64 address originally, right?

I tried to write 64.4.250.36:80 to the browser’s bar. It redirects me to www.paypal.com immediately.

What if you open http://64.4.250.37?

Redirects me to www.paypal.com.

Your screenshot is referring to an SSL issue. Maybe Paypal currently has some SSL issues on that particular machine.

In any case, it doesnt seem to be 1.1.1.1 related.