Skip to content
https://discordapp.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 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
TLS Certificate Expiry & Recommendations
46 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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: CDG)
Got: cf-ray: 9ed52aa83a355dcd-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9ed52aa83a355dcd-CDG
A+
DNS Records
5 A records, 96 ms lookup
PASS
5 A records, 96 ms lookup
Info::
Resolves to 5 IPv4 address(es)
Got: 162.159.129.233, 162.159.134.233, 162.159.135.233, 162.159.133.233, 162.159.130.233
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: gabe.ns.cloudflare.com, sima.ns.cloudflare.com
Info::
5 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 96 ms
Got: 96 ms
A162.159.129.233, 162.159.134.233, 162.159.135.233, 162.159.133.233, 162.159.130.233
AAAA
CNAME
NSgabe.ns.cloudflare.com, sima.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
5508A8F48F
dust-domain-verification-kz9236=gJamMWiktWPTDezEQ9uvTDzyS
hubspot-domain-verification=YmIxMDNhZDEtMzI3Mi00ZWNjLTk4MTYtNmViZGU5NzYyZDM5
loom-site-verification=3b8db7a74102494ba9569c862bbc5587
HjRfQW6OV2YOkDOgNju3gYI0_cx9H1iF
atlassian-domain-verification=JNe2Ze7P8p623k8f7xRaHDyQWb6VzLxjFga1tu8M7lmVXC0bo1...
autodesk-domain-verification=2sh4O6xiIc4ReP9Aee8h
google-site-verification=jtVaxAcfspCN94ECrH12n9XJhdqO6Y2j2u3eh1XsApE
gc-ai-domain-verification-h4p9zv=mTSLyVQqkAlNuctKXdWWZ7MLC
adobe-idp-site-verification=954e966634e7f12b8a9a2876a989bf5e7f5050a5192c3f529b99...
google-site-verification=27NMadvvj0pSQl1hkMaX3X5bwpjdFmE_FvX-MAgdLBE
logmein-verification-code=2d4b306a-e291-4dc9-a09f-2cc3277288cc
SPF v=spf1 include:_spf.google.com include:mail.zendesk.com include:sendgrid.net inc...
stripe-verification=1d56fec5a0f745dabfbe48592806853324fe50a8d4448c10e524136d1fac...
slack-domain-verification=wmXS8pleSDJ3LgREcHasvMfdkHmBbUvNI6nHNnJl
logmein-verification-code=e675be17-2988-4b0b-9e19-d6793fc28655
notion_verify_A}38XvVG2tiA3b6w4kU89}p~hasV-%G^E8U0.Evvp?^a==pC1]12+eXq]BgW+%hmod...
MS=CD44642CAC1658ABE588B1F34173984181355D4E
docker-verification=f765b7ff-5ce5-4f27-b00a-28091eddacce
zapier-domain-verification-challenge=d87a2680-bf27-4b61-8174-5ceed32bb8c7
google-site-verification=PmQRNDYVKwgF3tM6HulK5Fmmna3DSKklkjl-epmhplA
google-site-verification=ihjYpERVTt6QLWL2IBBLsEZroHPjP3vVQHQG97oXZlI
adobe-sign-verification=d19200aacd69c1b8e10cd1a5b47c91c3
apple-domain-verification=xPWro2NHlvCQs7LI
dropbox-domain-verification=66jnk5y945ew
google-site-verification=DGERr7gTRtGPVmghE_qE_w3X2kyTXdqiDVR2pBDpndQ
onetrust-domain-verification=3e11024ff11441678e3d59aa6b3a87bc
stripe-verification=b449d3730bb78d03e0744aa61ae3fa2f35f80572bff9e48ad9a192750829...
CAALookup not available with standard resolver
Resolved in 96 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.

A
Redirect Chain
1 redirect(s), 182 ms total
PASS
1 redirect(s), 182 ms total
Info::
Single redirect
Got: https://discordapp.com → https://discord.com/ (301)
Info::
Cross-domain redirect detected

https://discordapp.com

59 ms · HTTP/1.1

301

https://discord.com/

123 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://discordapp.com30159 msHTTP/1.1cloudflare
2https://discord.com/200123 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.discordapp.com/
200https://discordapp.com/

Preferred variant: non-www

HTTP → HTTPS

301http://discordapp.com/ https://discordapp.com/

Consistent

A+
Domain Intelligence
discordapp.com — via Cloudflare, Inc., 11 years, 3 months old, hosted on Cloudflare
PASS
discordapp.com — via Cloudflare, Inc., 11 years, 3 months old, hosted on Cloudflare
Info::
Domain registered until Feb 26, 2027 (10 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Cloudflare, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

228 days

February 26, 2027

SSL certificate

46 days

Issued by Google Trust Services

Domain age

11 years, 3 months

Registered February 26, 2015

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

162.159.129.233

Registrar

Cloudflare, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created February 26, 2015 (11 years, 3 months ago)
Expires February 26, 2027 (10 months)
Last Updated November 29, 2025
Name Servers gabe.ns.cloudflare.com, sima.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 162.159.129.233
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.3s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 86 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
29 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
20 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
87 ms
Total Time Total request time from DNS lookup through full response.
87 ms

Connection waterfall

DNS Lookup 29 ms TCP Connect 17 ms TLS Handshake 20 ms Server Processing 21 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