databricks.com: IP address, DNS records and WHOIS
Live lookup data for databricks.com: the IP addresses it resolves to, the DNS records it publishes, and its registration details. The data below is fetched when this page is built and refreshed daily.
At a glance
DNS records
A
| 13.33.153.48 | TTL 60 |
| 13.33.153.53 | TTL 60 |
| 13.33.153.83 | TTL 60 |
| 13.33.153.103 | TTL 60 |
AAAA
| 2600:9000:2021:1400:8:7feb:d180:93a1 | TTL 60 |
| 2600:9000:2021:1c00:8:7feb:d180:93a1 | TTL 60 |
| 2600:9000:2021:4a00:8:7feb:d180:93a1 | TTL 60 |
| 2600:9000:2021:5e00:8:7feb:d180:93a1 | TTL 60 |
| 2600:9000:2021:7e00:8:7feb:d180:93a1 | TTL 60 |
| 2600:9000:2021:8200:8:7feb:d180:93a1 | TTL 60 |
| 2600:9000:2021:d200:8:7feb:d180:93a1 | TTL 60 |
| 2600:9000:2021:d800:8:7feb:d180:93a1 | TTL 60 |
CNAME
No public records of this type are currently published.
MX
| aspmx.l.google.com | 10 |
| alt1.aspmx.l.google.com | 20 |
| alt2.aspmx.l.google.com | 20 |
| aspmx2.googlemail.com | 30 |
| aspmx3.googlemail.com | 30 |
| aspmx4.googlemail.com | 30 |
| aspmx5.googlemail.com | 30 |
NS
| ns1.databricks.com |
| ns2.databricks.com |
| ns3.databricks.com |
| ns4.databricks.com |
TXT
| nintex.64c1819b4e57291a7f904476 |
| nintex.6706f72ff44860f703c4eb2a |
| apple-domain-verification=jh4LRdliC3G9wlP9 |
| jamf-site-verification=u__nB7Pg6xkKogq0OcwdMg |
| canva-site-verification=2l7_ShHZm7F-Q0ShTy5hqA |
| doordash-verification=gVLZptaS1PIm7D51jfiqz8ckivqgaZ |
| openai-domain-verification=dv-bbyQW949WFLQyptpetWigelQ |
| openai-domain-verification=dv-uBiolSlNi39wfRhL5OF5tmVj |
SOA
- Primary nameserver
- ns1.databricks.com
- Hostmaster
- awsdns-hostmaster@amazon.com
- Serial
- 1
- Refresh
- 7200 s (2 hours)
- Retry
- 900 s (15 minutes)
- Expire
- 1209600 s (14 days)
- Minimum TTL
- 60 s (1 minute)
CAA
| 0 iodef "mailto:entsec-caa-monitoring@databricks.com" |
| 0 issue "1and1.digitalcertvalidation.com" |
| 0 issue "amazon.com" |
| 0 issue "amazonaws.com" |
| 0 issue "amazontrust.com" |
| 0 issue "awstrust.com" |
| 0 issue "cybertrust.ne.jp" |
| 0 issue "digicert.com" |
| 0 issue "digicert.ne.jp" |
| 0 issue "geotrust.com" |
| 0 issue "intermediatecertificate.digitalcertvalidation.com" |
| 0 issue "letsencrypt.org;validationmethods=dns-01,http-01" |
| 0 issue "pki.goog" |
| 0 issue "rapidssl.com" |
| 0 issue "stratossl.digitalcertvalidation.com" |
| 0 issue "thawte.com" |
| 0 issue "volusion.digitalcertvalidation.com" |
| 0 issue "www.digicert.com" |
| 0 issuewild "1and1.digitalcertvalidation.com" |
| 0 issuewild "amazon.com" |
| 0 issuewild "amazonaws.com" |
| 0 issuewild "amazontrust.com" |
| 0 issuewild "awstrust.com" |
| 0 issuewild "cybertrust.ne.jp" |
| 0 issuewild "digicert.com" |
| 0 issuewild "digicert.ne.jp" |
| 0 issuewild "geotrust.com" |
| 0 issuewild "intermediatecertificate.digitalcertvalidation.com" |
| 0 issuewild "letsencrypt.org;validationmethods=dns-01" |
| 0 issuewild "pki.goog" |
| 0 issuewild "rapidssl.com" |
| 0 issuewild "stratossl.digitalcertvalidation.com" |
| 0 issuewild "thawte.com" |
| 0 issuewild "volusion.digitalcertvalidation.com" |
| 0 issuewild "www.digicert.com" |
WHOIS registration data
- Registrar
- Amazon Registrar, Inc.
- Registered
- Jul 13, 2011
- Expires
- Jul 13, 2027
- Last changed
- Jun 8, 2026
- Status
- client transfer prohibited
- Nameservers
- ns1.databricks.com, ns2.databricks.com, ns3.databricks.com, ns4.databricks.com
- DNSSEC signed
- Yes
FAQ
databricks.com currently resolves to 13.33.153.48, 13.33.153.53, 13.33.153.83, 13.33.153.103, 2600:9000:2021:1400:8:7feb:d180:93a1, 2600:9000:2021:1c00:8:7feb:d180:93a1. Large sites often publish several addresses and rotate them, so the list can differ between checks and between locations.
databricks.com is registered through Amazon Registrar, Inc.. The registrant's identity is not published in the public registration record — most owners use a privacy service or the data is redacted.
databricks.com is served by ns1.databricks.com, ns2.databricks.com, ns3.databricks.com, ns4.databricks.com. These are the authoritative nameservers that publish its DNS records.
Run a fresh check
Records change. Run the live tools for an up-to-the-minute answer: