DNS records for slack.com
slack.com resolves to 4 IPv4 addresses, it is served by 4 nameservers (ns-166.awsdns-20.com), and accepts mail via 5 MX records.
A records (IPv4)
| TTL 59s | 18.134.215.41 |
| TTL 59s | 18.169.61.189 |
| TTL 59s | 18.169.120.191 |
| TTL 59s | 18.168.172.238 |
AAAA records (IPv6)
No records of this type.
MX records (mail servers)
| Priority 10 | aspmx2.googlemail.com |
| Priority 5 | alt1.aspmx.l.google.com |
| Priority 5 | alt2.aspmx.l.google.com |
| Priority 10 | aspmx3.googlemail.com |
| Priority 1 | aspmx.l.google.com |
NS records (nameservers)
| NS 1 | ns-166.awsdns-20.com |
| NS 2 | ns-606.awsdns-11.net |
| NS 3 | ns-1901.awsdns-45.co.uk |
| NS 4 | ns-1493.awsdns-58.org |
TXT records
| TXT 1 | OSSRH-54733 |
| TXT 2 | hubspot-developer-verification=OTE4NzYxYTgtMDUwZi00MzgzLTk2YTUtZDAwNjBlODg1MWM0 |
| TXT 3 | google-site-verification=KqX3Ngw0XEjz_0GVx_xwFFlCoO-bskhqU_lxv0Q77mk |
| TXT 4 | google-site-verification=QvelFPjIOe3Vavw0q-aAVYaAPKmWCRjmmVVEAjgfjQc |
| TXT 5 | v=spf1 include:_spf.qualtrics.com include:mail.zendesk.com include:_spfextra.slack.com -all |
| TXT 6 | google-site-verification=o2grd1TLmZZ8GrqbhVIFtzO2MRLTtSUpBBIBYfhQVCQ |
| TXT 7 | google-site-verification=2PK67oVPNyEtS1avSlr3PhH5nSiFuticbQv_bT4pM2k |
| TXT 8 | _0vidyxobp6x350odqhb4fo7fdxhmtq3 |
| TXT 9 | spycloud-domain-verification=02e4c0be-cf43-44e4-beaf-4f99702ca632 |
| TXT 10 | google-site-verification=efuXt5-oMr2CdNmVi6A9IO29KMKifpseD1qokxjWwcE |
| TXT 11 | google-site-verification=v-LLB__IhraaI7ZzuE3jvRFIm2vERPLzWoepAEZJtKQ |
| TXT 12 | google-site-verification=kB1KvgpSk9YkHsFmsj1VPI5YmDvfKctPxnplhGjyqtE |
SOA (Start of Authority)
| Primary NS | ns-1493.awsdns-58.org |
| Hostmaster | awsdns-hostmaster.amazon.com |
| Serial | 1 |
| Refresh | 7200s |
| Retry | 900s |
| Expire | 1209600s |
| Min TTL | 300s |
More lookups for slack.com
DNS records map a domain like slack.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.