slack.com
Domduck has read slack.com on 75 days across 8 sources, since 28 July 2026. The domain was registered in 1992. Its robots.txt blocks none of the 8 AI crawlers Domduck tracks.
Last checked .
100
What changed
75 days of readings- 8 October 2026 (2026-10-08)
- The certificate was renewed on 8 October 2026 and is valid to 5 January 2027.
- 5 October 2026 (2026-10-05)
- DNSSEC was enabled on 5 October 2026.
- 4 October 2026 (2026-10-04)
- DNSSEC was disabled on 4 October 2026.
- 3 October 2026 (2026-10-03)
- DNSSEC was enabled on 3 October 2026.
- 1 October 2026 (2026-10-01)
- DNSSEC was disabled on 1 October 2026.
- 30 September 2026 (2026-09-30)
- DNSSEC was enabled on 30 September 2026.
- 28 September 2026 (2026-09-28)
- DNSSEC was disabled on 28 September 2026.
- 27 September 2026 (2026-09-27)
- DNSSEC was enabled on 27 September 2026.
- 25 September 2026 (2026-09-25)
- DNSSEC was disabled on 25 September 2026.
- 24 September 2026 (2026-09-24)
- DNSSEC was enabled on 24 September 2026.
- 23 September 2026 (2026-09-23)
- DNSSEC was disabled on 23 September 2026.
- 22 September 2026 (2026-09-22)
- DNSSEC was enabled on 22 September 2026.
Domain Rating
77 daysA 0 to 100 score of how strong a domain’s backlink profile is, on a logarithmic scale, so the distance from 70 to 80 is far larger than from 10 to 20.
Popularity rank
77 days, lower is betterPosition in the Tranco list, a research ranking of the million most popular domains averaged over thirty days so a single day’s traffic spike cannot move it.
AI crawler policy
Serves llms.txtNo ChatGPT browsing or training
No ChatGPT search surface
No Claude retrieval
No Perplexity citation
Out of Gemini and AI Overviews grounding, Search ranking unaffected
Out of Apple Intelligence training
Out of most open training corpora
Out of TikTok and Doubao
Read from slack.com/robots.txt. “Not named” means the file says nothing about that agent, which is not the same as allowing it: a catch-all rule added later blocks it without anyone deciding to.
What the domain itself says
read directly, not from a vendor- Issuer
- Let's Encrypt
- Valid
- Yes
- Expires
- 2027-01-05
- Protocol
- TLSv1.3
- Names covered
- 2
- A records
- 3
- AAAA records
- 0
- Mail exchangers
- 5
- Nameservers
- ns-1493.awsdns-58.org, ns-166.awsdns-20.com, ns-1901.awsdns-45.co.uk, ns-606.awsdns-11.net
- DMARC policy
- reject
- Registered
- 1992-10-21
- Registrar
- MarkMonitor Inc.
- Registry status
- client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
How slack.com compares to other .com domains
Questions
- Does slack.com block GPTBot?
- No. slack.com's robots.txt does not disallow GPTBot, though it does not name the agent either.
- Does slack.com publish an llms.txt file?
- Yes. slack.com serves an llms.txt file.
- When was slack.com registered?
- 21 October 1992, through MarkMonitor Inc..
- Who issues slack.com's certificate?
- Let's Encrypt.
How this page is made
Every number on this page is a measurement Domduck took itself or read from a public source, on a stated date. Nothing here is written by a language model. Where a value has not changed, no sentence is generated about it.
First reading . 8 sources, 75 days with at least one reading. The popularity rank comes from the Tranco list; the registration record from RDAP, which ICANN requires registries to publish. The certificate, the DNS records and the crawler policy are read by Domduck directly from slack.com.