Skip to content
https://ziglang.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
97
GRADE
A+
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
7 PASS 1 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.

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

Certificate validity

64
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, 127 ms lookup
PASS
1 A records, 127 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 65.109.105.178
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a01:4f9:3051:4bd2::2
Info::
4 nameserver(s) configured
Got: ns-1467.awsdns-55.org, ns-1904.awsdns-46.co.uk, ns-47.awsdns-05.com, ns-975.awsdns-57.net
Info::
1 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: 127 ms
Got: 127 ms
A65.109.105.178
AAAA2a01:4f9:3051:4bd2::2
CNAME—
NSns-1467.awsdns-55.org, ns-1904.awsdns-46.co.uk, ns-47.awsdns-05.com, ns-975.awsdns-57.net
MX
10 mail.ziglang.org
TXT
SPF v=spf1 ip4:108.61.23.47 -all
CAALookup not available with standard resolver
Resolved in 127 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://ziglang.org

https://ziglang.org

424 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ziglang.org200424 msHTTP/1.1nginx/1.18.0
A+
IPv6 Readiness
IPv6 reachable (97 ms)
PASS
IPv6 reachable (97 ms)
Info::
IPv6 is configured and reachable at 2a01:4f9:3051:4bd2::2
Got: 97 ms connect
IPv6 Ready
AAAA Records 2a01:4f9:3051:4bd2::2 Connection Reachable (97 ms)
A
Crawlability
no robots.txt, sitemap with 14 URLs
PASS
no robots.txt, sitemap with 14 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14 entries
Info::
Sitemap index with 14 child sitemaps

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml 200 OK
Type Sitemap Index URLs 14 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.ziglang.org/
200https://ziglang.org/

HTTP → HTTPS

301http://ziglang.org/ → https://ziglang.org/

Consistent

A+
Domain Intelligence
ziglang.org — via NameCheap, Inc., 10 years, 1 months old
PASS
ziglang.org — via NameCheap, Inc., 10 years, 1 months old
Info::
Domain registered until Apr 9, 2030 (4 years 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: NameCheap, Inc.
Domain expiry

1331 days

April 9, 2030

SSL certificate

64 days

Issued by Let's Encrypt

Domain age

10 years, 1 months

Registered April 9, 2016

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a01:4f9:3051:4bd2::2

Registrar

NameCheap, Inc.

Lock status unknown 4 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
Registrar NameCheap, Inc.
Created April 9, 2016 (10 years, 1 months ago)
Expires April 9, 2030 (4 years)
Last Updated March 10, 2021
Name Servers ns-1467.awsdns-55.org, ns-1904.awsdns-46.co.uk, ns-47.awsdns-05.com, ns-975.awsdns-57.net
DNSSEC Not enabled
Hosting
IP Address 2a01:4f9:3051:4bd2::2
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

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 97 ms TLS Handshake 99 ms Server Processing 98 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