Skip to content
https://discord.gg

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
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

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 23 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 23 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
38 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable DNSSEC on your domain for DNS spoofing protection
  • 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: 9ed4c2aa69d9bb36-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9ed4c2aa69d9bb36-CDG
A+
DNS Records
5 A records, 30 ms lookup
PASS
5 A records, 30 ms lookup
Info::
Resolves to 5 IPv4 address(es)
Got: 162.159.133.234, 162.159.134.234, 162.159.136.234, 162.159.135.234, 162.159.130.234
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: 30 ms
Got: 30 ms
A162.159.133.234, 162.159.134.234, 162.159.136.234, 162.159.135.234, 162.159.130.234
AAAA
CNAME
NSgabe.ns.cloudflare.com, sima.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
google-site-verification=myBwnC_3tX4Kaw_0os4oy_urABnW_SB6osr_6uxblIY
google-site-verification=W3bS5jNE3UOjccTXit2Ec9uo83D0leVlfpYH04PSEvg
SPF v=spf1 include:_spf.google.com ~all
apple-domain-verification=zozWMNbMyCg4di2h
CAALookup not available with standard resolver
Resolved in 30 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), 176 ms total
PASS
1 redirect(s), 176 ms total
Info::
Single redirect
Got: https://discord.gg → https://discord.com (301)
Info::
Cross-domain redirect detected

https://discord.gg

60 ms · HTTP/1.1

301

https://discord.com

116 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://discord.gg30160 msHTTP/1.1cloudflare
2https://discord.com200116 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.discord.gg/
200https://discord.gg/

Preferred variant: non-www

HTTP → HTTPS

301http://discord.gg/ https://discord.gg/

Consistent

A+
Domain Intelligence
discord.gg — via Gandi SAS, 11 years, 3 months old, hosted on Cloudflare
PASS
discord.gg — via Gandi SAS, 11 years, 3 months old, hosted on Cloudflare
Info::
Registrar: Gandi SAS
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

Unknown

SSL certificate

38 days

Issued by Google Trust Services

Domain age

11 years, 3 months

Registered February 26, 2015

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

162.159.130.234

Registrar

Gandi SAS

Unlocked 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Gandi SAS
Created February 26, 2015 (11 years, 3 months ago)
Name Servers gabe.ns.cloudflare.com, sima.ns.cloudflare.com
Hosting
IP Address 162.159.130.234
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: whois (0.7s)

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 91 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 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.
91 ms
Total Time Total request time from DNS lookup through full response.
92 ms

Connection waterfall

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