iPGaze

DNS records for bitbucket.org

bitbucket.org resolves to 3 IPv4 addresses and 3 IPv6 addresses, it is served by 4 nameservers (ns-445.awsdns-55.com), and accepts mail via 2 MX records.

Run a live lookup ↗

A records (IPv4)

TTL 59s185.166.142.23
TTL 59s185.166.142.21
TTL 59s185.166.142.22

AAAA records (IPv6)

TTL 59s2401:1d80:3214:1:0:bbc:1:df7c
TTL 59s2401:1d80:3214:2:0:bbc:1:df7c
TTL 59s2401:1d80:3214::bbc:1:df7c

MX records (mail servers)

Priority 10mxa-001d9801.gslb.pphosted.com
Priority 10mxb-001d9801.gslb.pphosted.com

NS records (nameservers)

NS 1ns-445.awsdns-55.com
NS 2ns-1746.awsdns-26.co.uk
NS 3ns-1305.awsdns-35.org
NS 4ns-584.awsdns-09.net

TXT records

TXT 1status-page-domain-verification=3fbwzqm8vjhr
TXT 2facebook-domain-verification=84vhrka086if54vvfvdk2ezuvfdwyq
TXT 3google-site-verification=p99sO7SVcXanHfj-NuQZJKocj3_4Hkws2ZNbbieLW1M
TXT 4google-site-verification=X2bEMlmrK-ok6sdGW5j0jsTGCV7IqlqYQxVTV9MQngg
TXT 5atlassian-domain-verification=ZRphniOpyvhHV76mRmxnLkHJVrKnbeOIxmhbxb8PF6AarX0FypthxYB/r5XpVC2E
TXT 6_kc0m4lhl1awr95c7d38tvu102h1x8jf.dcv.digicert.com
TXT 7v=spf1 ip4:167.89.90.3/32 ip4:167.89.37.79/32 ip4:167.89.38.16/32 ip4:167.89.38.188/32 ip4:167.89.38.218/32 include:atlassian.mail.e.sparkpost.com a:001.lax.mailroute.net include:stspg-customer.com include:_spf.atlassian.net -all
TXT 8google-site-verification=QWfM0kROcuH3GIqpbpGM-jg3ajJyj4Ie5t_LZisV6E0
TXT 9google-site-verification=oFmSUhmR77qRC-e8T1kL-eaO7pvT8XUmpw1G0p-lWqM
TXT 10google-site-verification=BIhAfAJXWYr-hSVf3rOpm7IIWSX6mA7d0Na7t-GaEwA
TXT 11_1tb6ruf8jsqqv5hyasqil8wwbby7knz.dcv.digicert.com

SOA (Start of Authority)

Primary NSns-584.awsdns-09.net
Hostmasterawsdns-hostmaster.amazon.com
Serial1
Refresh7200s
Retry900s
Expire1209600s
Min TTL86400s

More lookups for bitbucket.org

DNS records map a domain like bitbucket.org 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.