iPGaze

DNS records for paypal.com

paypal.com resolves to 3 IPv4 addresses, it is served by 4 nameservers (pdns100.ultradns.net), and accepts mail via 2 MX records.

Run a live lookup ↗

A records (IPv4)

TTL 27s162.159.141.96
TTL 27s151.101.3.1
TTL 27s151.101.195.1

AAAA records (IPv6)

No records of this type.

MX records (mail servers)

Priority 10mx2.paypalcorp.com
Priority 10mx1.paypalcorp.com

NS records (nameservers)

NS 1pdns100.ultradns.net
NS 2ns1-pchnet.paypal.com
NS 3pdns100.ultradns.com
NS 4ns2-pchnet.paypal.com

TXT records

TXT 1docker-verification=2deb3c1f-56d2-4fe4-8a09-d48b7bf8a918
TXT 2globalsign-domain-verification=KXa3jn_dNODlTVQ4eg1Wx3vA-RrHZ2K7iLQN0vdJBx
TXT 3v=spf1 include:pp._spf.paypal.com include:3ph1._spf.paypal.com include:3ph2._spf.paypal.com include:3ph3._spf.paypal.com include:3ph4._spf.paypal.com include:sendgrid.net include:aspmx.pardot.com ~all
TXT 4MS=ms95960309
TXT 5mgf84gx1cv1c759pmjqx0wnths9ss9f6
TXT 6mgverify=e00c4bf7480ee22be851faa9acd20e41b8fd0f7b75b434bbe38aa257e5aae3a0
TXT 7workplace-domain-verification=F7ezsH9uapvYDGd2VtPARy1qq9ymN6
TXT 8Notion_verify_uVqjH2PpjVthR9xxfR5BZGsuYGtqb6Za4uDHPaA917v5Cg5J0rRwiATz84PWHZh8Px7vFK
TXT 9stripe-verification=549bef27619f14f935a84c6a23492e80f49ff57a341d9ddc74d8486881cd0d8c
TXT 10atlassian-domain-verification=Q8BdHlO6NYSN5njfC2rlbPQxksVfADlcxarxq4fesYJErtGKylvfcfyfwrPD/wnv
TXT 11adobe-idp-site-verification=11600efbec96c0e73dd8820cd33ca906ec4302aea4487d208a42a2b01806144c
TXT 12intersight=6d86ec09a7c6926c6f9b8eff8ef0ef06679d84aab4999756a0920a8d430ed8ae

SOA (Start of Authority)

Primary NSppdns.paypal.com
Hostmasterhostmaster.paypal.com
Serial2012399912
Refresh7200s
Retry600s
Expire1209600s
Min TTL300s

More lookups for paypal.com

DNS records map a domain like paypal.com to the servers and services behind it. A and AAAA records point to IPv4 and IPv6 addresses, MX records route email, NS records delegate authority to nameservers, TXT records hold verification and policy data (such as SPF), and the SOA record describes the zone. Values are cached by resolvers for the length of each record's TTL, so a recent change may not appear everywhere at once. To check any other domain, use the DNS Lookup tool.