Skip to content
https://www.discord.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1309 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1309 B Sitemaps referenced 0 User-agents *, Twitterbot, nsa Blocking No — crawling allowed
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: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.discord.com/
200https://discord.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.discord.com/ https://discord.com/

Consistent

B
TLS Certificate Expiry & Recommendations
55 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

55
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: 9e8ba19cfc439a64-AMS
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8ba19cfc439a64-AMS
A
DNS Records
5 A records, 12 ms lookup
PASS
5 A records, 12 ms lookup
Info::
Resolves to 5 IPv4 address(es)
Got: 162.159.128.233, 162.159.135.232, 162.159.136.232, 162.159.137.232, 162.159.138.232
Info::
No IPv6 (AAAA) records
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 12 ms
Got: 12 ms
A162.159.128.233, 162.159.135.232, 162.159.136.232, 162.159.137.232, 162.159.138.232
AAAA
CNAME
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 12 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 66 ms total
PASS
1 redirect(s), 66 ms total
Info::
Single redirect
Got: https://www.discord.com → https://discord.com/ (301)
Info::
WWW normalization redirect

https://www.discord.com

19 ms · HTTP/1.1

301

https://discord.com/

47 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.discord.com30119 msHTTP/1.1cloudflare
2https://discord.com/20047 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
discord.com — via Cloudflare, Inc., 25 years, 9 months old, hosted on Cloudflare
PASS
discord.com — via Cloudflare, Inc., 25 years, 9 months old, hosted on Cloudflare
Info::
Domain registered until Nov 6, 2026 (7 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Cloudflare, Inc.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

81 days

November 6, 2026

SSL certificate

55 days

Issued by Google Trust Services

Domain age

25 years, 9 months

Registered November 6, 2000

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

162.159.138.232

Registrar

Cloudflare, Inc.

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar Cloudflare, Inc.
Created November 6, 2000 (25 years, 9 months ago)
Expires November 6, 2026 (7 months)
Last Updated August 8, 2025
Name Servers gabe.ns.cloudflare.com, sima.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 162.159.138.232
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.3s)
A+
HTTP Probe Timing
Total 17 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
17 ms
Total Time Total request time from DNS lookup through full response.
17 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 4 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback