Skip to content
https://c2.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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

Crawl-delay: 30
Disallow: /~ward/sudokant.cgi

Disallow: /wiki/history

Disallow: /~ward/morse/ve

Disallow: /lisa

Disallow: /~ward/wikitect

Disallow: /cgi/allpages

Disallow: /cgi-bin/allpages

Disallow: /cgi/blockme

Disallow: /cgi-bin/blockme

Disallow: /cgi/bridges.zip

Disallow: /cgi-bin/bridges.zip

Disallow: /cgi/cam.cgi

Disallow: /cgi-bin/cam.cgi

Disallow: /cgi/eprime

Disallow: /cgi-bin/eprime

Disallow: /cgi/favicon.ico

Disallow: /cgi-bin/favicon.ico

Disallow: /cgi/fullSearch

Disallow: /cgi-bin/fullSearch

Disallow: /cgi/grid

Disallow: /cgi-bin/grid

Disallow: /cgi/grid-length

Disallow: /cgi-bin/grid-length

Disallow: /cgi/grid-words

Disallow: /cgi-bin/grid-words

Disallow: /cgi/histDiff.cgi

Disallow: /cgi-bin/histDiff.cgi

Disallow: /cgi/imagemap

Disallow: /cgi-bin/imagemap

Disallow: /cgi/isbn

Disallow: /cgi-bin/isbn

Disallow: /cgi/kaweahits

Disallow: /cgi-bin/kaweahits

Disallow: /cgi/likeGameData

Disallow: /cgi-bin/likeGameData

Disallow: /cgi/links

Disallow: /cgi-bin/links

Disallow: /cgi/locale

Disallow: /cgi-bin/locale

Disallow: /cgi/longs.cgi

Disallow: /cgi-bin/longs.cgi

Disallow: /cgi/mb

Disallow: /cgi-bin/mb

Disallow: /cgi/onTopic

Disallow: /cgi-bin/onTopic

Disallow: /cgi/orphanWikiPages

Disallow: /cgi-bin/orphanWikiPages

Disallow: /cgi/outline

Disallow: /cgi-bin/outline

Disallow: /cgi/quickChanges

Disallow: /cgi-bin/quickChanges

Disallow: /cgi/quickDiff

Disallow: /cgi-bin/quickDiff

Disallow: /cgi/quickDiff.cgi

Disallow: /cgi-bin/quickDiff.cgi

Disallow: /cgi/quickEdits

Disallow: /cgi-bin/quickEdits

Disallow: /cgi/RecentChanges

Disallow: /cgi-bin/RecentChanges

Disallow: /cgi/separation

Disallow: /cgi-bin/separation

Disallow: /cgi/shorts.cgi

Disallow: /cgi-bin/shorts.cgi

Disallow: /cgi/squeak10

Disallow: /cgi-bin/squeak10

Disallow: /cgi/squeak.zip

Disallow: /cgi-bin/squeak.zip

Disallow: /cgi/survey

Disallow: /cgi-bin/survey

Disallow: /cgi/test

Disallow: /cgi-bin/test

Disallow: /cgi/tile

Disallow: /cgi-bin/tile

Disallow: /cgi/tiny

Disallow: /cgi-bin/tiny

Disallow: /cgi/topten

Disallow: /cgi-bin/topten

Disallow: /cgi/tour

Disallow: /cgi-bin/tour

Disallow: /cgi/translate

Disallow: /cgi-bin/translate

Disallow: /cgi/wantedWikiPages

Disallow: /cgi-bin/wantedWikiPages

Disallow: /cgi/wikiDiff

Disallow: /cgi-bin/wikiDiff

Disallow: /cgi/wikiList

Disallow: /cgi-bin/wikiList

Disallow: /cgi/wikiNames

Disallow: /cgi-bin/wikiNames

Disallow: /cgi/wikiOptions

Disallow: /cgi-bin/wikiOptions

Disallow: /cgi/wikiPages

Disallow: /cgi-bin/wikiPages

Disallow: /cgi/wikiReadWrite

Disallow: /cgi-bin/wikiReadWrite

Disallow: /cgi/wikiRss

Disallow: /cgi-bin/wikiRss

Disallow: /cgi/wikiSig

Disallow: /cgi-bin/wikiSig

Disallow: /cgi/like

Disallow: /cgi-bin/like

Disallow: /cgi/x-posts

Disallow: /cgi-bin/x-posts
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::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

https://www.c2.com/
200https://c2.com/

HTTP → HTTPS

200http://c2.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

31
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
A+
DNS Records
1 A records, 67 ms lookup
PASS
1 A records, 67 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 198.199.96.69
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns3.digitalocean.com, ns2.digitalocean.com, ns1.digitalocean.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: 67 ms
Got: 67 ms
A198.199.96.69
AAAA—
CNAME—
NSns3.digitalocean.com, ns2.digitalocean.com, ns1.digitalocean.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
SPF v=spf1 a include:_spf.google.com -all
CAALookup not available with standard resolver
Resolved in 67 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://c2.com

https://c2.com

480 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://c2.com200480 msHTTP/1.1Apache
A+
Domain Intelligence
c2.com — via Name.com, Inc., 31 years, 11 months old, hosted on DigitalOcean
PASS
c2.com — via Name.com, Inc., 31 years, 11 months old, hosted on DigitalOcean
Info::
Domain registered until Oct 22, 2026 (6 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: Name.com, 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: DigitalOcean
Got: AS14061
Domain expiry

128 days

October 22, 2026

SSL certificate

31 days

Issued by Let's Encrypt

Domain age

31 years, 11 months

Registered October 23, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

DigitalOcean

ASN AS14061

198.199.96.69

Registrar

Name.com, Inc.

Unlocked 3 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 Name.com, Inc.
Created October 23, 1994 (31 years, 11 months ago)
Expires October 22, 2026 (6 months)
Last Updated September 30, 2025
Name Servers ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
DNSSEC Not enabled
Hosting
IP Address 198.199.96.69
ASN AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US)
Provider DigitalOcean
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 65 ms TCP Connect 164 ms TLS Handshake 166 ms Server Processing 164 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