Skip to content
https://fsc.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
B
Domain Intelligence
fsc.org — via Mesh Digital Limited, 29 years, 4 months old
REVIEW
fsc.org — via Mesh Digital Limited, 29 years, 4 months old
Critical::
Domain expires in 17 days
This domain expires on May 9, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires May 9, 2026
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: Mesh Digital Limited
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

EXPIRED

May 9, 2026

SSL certificate

15 days

Issued by Certainly

Domain age

29 years, 4 months

Registered May 8, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a04:4e42:9::765

Registrar

Mesh Digital Limited

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Mesh Digital Limited
Created May 8, 1997 (29 years, 4 months ago)
Expires May 9, 2026 (17 days)
Last Updated May 13, 2025
Name Servers ns67.domaincontrol.com, ns68.domaincontrol.com
DNSSEC Not enabled
Hosting
IP Address 2a04:4e42:9::765
Data source: rdap (0.3s)

This domain expires on May 9, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

C
TLS Certificate Expiry & Recommendations
Action
15 days until leaf cert expires — 6 issues to address
REVIEW

Certificate validity

15
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 15 days remaining
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 32 ms lookup
PASS
1 A records, 32 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 151.101.38.253
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: 2a04:4e42:9::765
Info::
2 nameserver(s) configured
Got: ns68.domaincontrol.com, ns67.domaincontrol.com
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: 32 ms
Got: 32 ms
A151.101.38.253
AAAA2a04:4e42:9::765
CNAME
NSns68.domaincontrol.com, ns67.domaincontrol.com
MX
0 fsc-org.mail.protection.outlook.com
TXT
nm1bt89sp514jf04s9rh11ee4m
rxZAp1tMBdnYTFmzagSFOiol77hZfASohxo44ErA7sFFT1nE0WAiuY/IFrW2bJVxjF6WutWdU6xFotRs...
docusign=b577d9dc-54c8-466c-bc42-4af76c83d419
atlassian-sending-domain-verification=b02f59fc-31bc-421d-98d1-aa4361e80654
SPF v=spf1 mx a include:spf.protection.outlook.com include:ispgateway.de ip4:212.79....
miro-verification=1ddb3699cc5e3b30d1c259d8718c615e4c2d4f0b
docusign=9502ff38-4767-40fb-85e3-614481b3972f
glo7fise0jnfjs9c0mu9oqe4bd
pardot659853=dab9b8985d6da1173eed64f7714ccdead13848732298f820e0af8eb296503e0d
google-site-verification=USjId2zSU1HM9k1xi6gwU13J1FWJ9oUN8E7itJsTv0s
google-site-verification=agKkTT7GptwcbcEl9ncNBaUHovEra0C2eB8wpU5ZsN8
MS=ms24768330
CAALookup not available with standard resolver
Resolved in 32 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
1 redirect(s), 202 ms total
PASS
1 redirect(s), 202 ms total
Info::
Single redirect
Got: https://fsc.org → https://fsc.org/en (301)

https://fsc.org

100 ms · HTTP/1.1

301

https://fsc.org/en

102 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fsc.org301100 msHTTP/1.1nginx
2https://fsc.org/en200102 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (30 ms)
PASS
IPv6 reachable (30 ms)
Info::
IPv6 is configured and reachable at 2a04:4e42:9::765
Got: 30 ms connect
IPv6 Ready
AAAA Records 2a04:4e42:9::765 Connection Reachable (30 ms)
A+
Crawlability
robots.txt present, sitemap with 319 URLs
PASS
robots.txt present, sitemap with 319 URLs
Info::
robots.txt is present
Got: 2064 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 319 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 2064 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed

Disallow: /media/
Disallow: /media/*
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.fsc.org/
200https://fsc.org/

Preferred variant: non-www

HTTP → HTTPS

301http://fsc.org/ https://fsc.org/

Consistent

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

Connection waterfall

DNS Lookup 33 ms TCP Connect 30 ms TLS Handshake 32 ms Server Processing 38 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT, MISS, MISS, MISS)
PASS
Fastly (HIT, MISS, MISS, MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-ams2100131-AMS, cache-ams2100131-AMS, cache-ams2100131-AMS, cache-ams2100133-AMS
Info::
CDN cache status: HIT, MISS, MISS, MISS
CDN Detected: Fastly
Provider Fastly Cache Status HIT, MISS, MISS, MISS Evidence x-served-by: cache-ams2100131-AMS, cache-ams2100131-AMS, cache-ams2100131-AMS, cache-ams2100133-AMS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback