Skip to content
https://www.signal.org

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 Singapore, Singapore
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

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

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

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 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.signal.org/
200https://signal.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.signal.org/ https://signal.org/

Consistent

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

Certificate validity

62
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: SIN)
Got: cf-ray: 9e8bb1caac935f6e-SIN
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8bb1caac935f6e-SIN
A
DNS Records
2 A records, 10 ms lookup
PASS
2 A records, 10 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.10.47, 104.18.11.47
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:a2f, 2606:4700::6812:b2f
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 10 ms
Got: 10 ms
A104.18.10.47, 104.18.11.47
AAAA2606:4700::6812:a2f, 2606:4700::6812:b2f
CNAME
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 10 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 74 ms total
PASS
1 redirect(s), 74 ms total
Info::
Single redirect
Got: https://www.signal.org → https://signal.org/ (301)
Info::
WWW normalization redirect

https://www.signal.org

22 ms · HTTP/1.1

301

https://signal.org/

53 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.signal.org30122 msHTTP/1.1cloudflare
2https://signal.org/20053 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:a2f, 2606:4700::6812:b2f
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:a2f, 2606:4700::6812:b2f Connection Reachable (1 ms)
A+
Domain Intelligence
signal.org — via MarkMonitor Inc., 25 years, 4 months old
PASS
signal.org — via MarkMonitor Inc., 25 years, 4 months old
Info::
Domain registered until Apr 15, 2028 (2 years remaining)
Info::
DNSSEC is enabled
Info::
Registrar: MarkMonitor Inc.
Domain expiry

643 days

April 15, 2028

SSL certificate

62 days

Issued by Google Trust Services

Domain age

25 years, 4 months

Registered April 15, 2001

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:a2f

Registrar

MarkMonitor Inc.

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar MarkMonitor Inc.
Created April 15, 2001 (25 years, 4 months ago)
Expires April 15, 2028 (2 years)
Last Updated June 8, 2025
Name Servers casey.ns.cloudflare.com, zita.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2606:4700::6812:a2f
Data source: rdap (0.8s)
A+
HTTP Probe Timing
Total 20 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
7 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
20 ms
Total Time Total request time from DNS lookup through full response.
21 ms

Connection waterfall

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