Skip to content
https://thecrimson.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1738 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 1738 B Sitemaps referenced 0 User-agents Google-Extended, GPTBot, *, meta-externalagent, Amazonbot, Applebot-Extended, Bytespider, CCBot, ClaudeBot, CloudflareBrowserRenderingCrawler Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content


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.thecrimson.com/
200https://thecrimson.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://thecrimson.com/ https://thecrimson.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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: GRU)
Got: cf-ray: 9f07e92b5b0c0126-GRU
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f07e92b5b0c0126-GRU
A+
DNS Records
3 A records, 196 ms lookup
PASS
3 A records, 196 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.10.24, 172.67.69.155, 104.26.11.24
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:b18, 2606:4700:20::681a:a18, 2606:4700:20::ac43:459b
Info::
2 nameserver(s) configured
Got: chan.ns.cloudflare.com, yichun.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: 196 ms
Got: 196 ms
A104.26.10.24, 172.67.69.155, 104.26.11.24
AAAA2606:4700:20::681a:b18, 2606:4700:20::681a:a18, 2606:4700:20::ac43:459b
CNAME
NSchan.ns.cloudflare.com, yichun.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
8 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
google-site-verification=0gedn3m1G899nbBiuVoT5eSkhhKSn6dlWV8ZVqUrWAA
google-site-verification=Bc2mavk4zJ06JnNGlSdJAaPXsQeWGkG5KIKJMwYa4VA
google-site-verification=S8W2lMDWzUGmvXg0weczzkaBMDKULjVqRLw4X_FGC_A
google-site-verification=fdluDl-kC_f4IyybfhURNvCyMLMOcOpBi_Mptm4TWv4
google-site-verification=hB3V4xG4hjpF48YyVB0F7s0CkL6hU_Zo3LxHYZb-j1o
google-site-verification=hhPRNRXS8gFocM89wq9A8-B-mR_l0xeM1p9BXKJqtUY
spf2.0/pra include:amazonses.com ?all
SPF v=spf1 include:amazonses.com ?all
CAALookup not available with standard resolver
Resolved in 196 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), 217 ms total
PASS
1 redirect(s), 217 ms total
Info::
Single redirect
Got: https://thecrimson.com → https://www.thecrimson.com/ (301)
Info::
WWW normalization redirect

https://thecrimson.com

22 ms · HTTP/1.1

301

https://www.thecrimson.com/

195 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://thecrimson.com30122 msHTTP/1.1cloudflare
2https://www.thecrimson.com/200195 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::681a:b18, 2606:4700:20::681a:a18, 2606:4700:20::ac43:459b
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::681a:b18, 2606:4700:20::681a:a18, 2606:4700:20::ac43:459b Connection Reachable (2 ms)
A+
Domain Intelligence
thecrimson.com — via Tucows Domains Inc., 29 years, 2 months old
PASS
thecrimson.com — via Tucows Domains Inc., 29 years, 2 months old
Info::
Domain registered until Jul 3, 2030 (4 years, 3 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Tucows Domains 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.
Domain expiry

1478 days

July 3, 2030

SSL certificate

71 days

Issued by Google Trust Services

Domain age

29 years, 2 months

Registered July 4, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::ac43:459b

Registrar

Tucows Domains Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows Domains Inc.
Created July 4, 1997 (29 years, 2 months ago)
Expires July 3, 2030 (4 years, 3 months)
Last Updated December 7, 2025
Name Servers chan.ns.cloudflare.com, yichun.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::ac43:459b
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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 27 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
9 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
9 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
27 ms
Total Time Total request time from DNS lookup through full response.
27 ms

Connection waterfall

DNS Lookup 9 ms TCP Connect 2 ms TLS Handshake 9 ms Server Processing 7 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