discord.com
Looks Normal
Standard signals observed
This reflects observed technical signals, not a judgment of the website's intent or safety. Wondering if Discord is legit? Below you'll find technical signals for discord.com including domain age, HTTPS security, DNS records, and redirect behavior to help you decide if this website is trustworthy.
The domain discord.com hosts an active website with DNS records managed via Cloudflare (inferred from nameservers). It uses multiple IP addresses and enforces HTTPS, redirecting HTTP requests to a secure connection. The SSL certificate is a valid wildcard type issued by Google Trust Services, expiring in April 2026. The domain has been registered for 25 years through Cloudflare, Inc. and is set to expire in November 2026. The site leverages Cloudflare and Webflow technologies. These signals describe technical characteristics only and do not indicate intent or safety.
Final URL:
https://discord.com/
Redirect chain
http://discord.com/
→
https://discord.com/
https://discord.com/
Expires in 63 days
Certificate details
Subject: /CN=discord.com
Issuer: /C=US/O=Google Trust Services/CN=WE1
Chain: 3 certificates
Subject Alt Names (2)
discord.com
matches
*.discord.com
Based on nameserver patterns, DNS appears to be hosted via Cloudflare, a widely-used DNS and CDN provider.
IP addresses & nameservers
A: 162.159.136.232, 162.159.137.232, 162.159.135.232, 162.159.138.232, 162.159.128.233
NS: gabe.ns.cloudflare.com, sima.ns.cloudflare.com
MX records (5)
TXT records (10)
apple-domain-verification=UP89cBit9taWldL9docusign=90632817-c176-45ac-9297-96916059c0c5slack-domain-verification=hb2Jt7Z5kT0NqJOuGUM2P6L3ZihqWD3...google-site-verification=4lTw99D7TJimzNkaj9WtUoOpZoXad73h...google-site-verification=AkZq_nCggw5fS3x2crQxF9I_9MEdqqWI...+ 5 more
More details
Last changed: Aug 08, 2025
Status: client delete prohibited client transfer prohibited client update prohibited +3 more
Nameservers: GABE.NS.CLOUDFLARE.COM, SIMA.NS.CLOUDFLARE.COM
These directives apply to crawlers requesting this host.
Directive breakdown
Raw content
User-agent: * Allow: /api/v*/store Allow: /api/v*/applications Allow: /api/v*/application-directory-static Allow: /api/v*/invite Allow: /api/v*/discovery Allow: /api/discovery Allow: /invite Allow: /invite/ Allow: /terms Allow: /privacy Disallow: /channels Disallow: /channels/ Disallow: /verify Disallow: /verify/ Disallow: /reset Disallow: /reset/ Disallow: /authorize-ip Disallow: /authorize-ip/ Disallow: /reject-ip Disallow: /reject-ip/ Disallow: /reject-mfa Disallow: /reject-mfa/ Disallow: /oauth2 Disallow: /oauth2/ Disallow: /api Disallow: /api/ Disallow: /widget Disallow: /widget/ Disallow: /profile/ Disallow: /report-review Disallow: /report-review/ Disallow: /store/skus/ Disallow: /wasntme Disallow: /wasntme/ User-agent: Twitterbot Disallow: /channels Disallow: /channels/ Disallow: /verify Disallow: /verify/ Disallow: /reset Disallow: /reset/ Disallow: /authorize-ip Disallow: /authorize-ip/ Disallow: /reject-ip Disallow: /reject-ip/ Disallow: /reject-mfa Disallow: /reject-mfa/ Disallow: /report-review Disallow: /report-review/ Disallow: /oauth2 Disallow: /oauth2/ Disallow: /api Disallow: /api/ Disallow: /widget Disallow: /widget/ Disallow: /profile/ Allow: /api/v*/application-directory-static Allow: /invite Allow: /invite/ Allow: /terms Allow: /privacy User-agent: nsa Disallow: /
Robots.txt directives are advisory instructions for crawlers and do not enforce access control.
Detection evidence
Technologies detected from HTTP headers and HTML patterns. Detection is passive and may not capture all technologies.