Skip to content
https://transparency.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from New York, United Stated
308 Permanent Redirect
Checks
9
5 PASS 4 REVIEW
B
Redirect Chain
2 redirect(s), 174 ms total
REVIEW
2 redirect(s), 174 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect

https://transparency.org

39 ms · HTTP/1.1

308

https://www.transparency.org/

62 ms · HTTP/1.1

301

https://www.transparency.org/en/

73 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://transparency.org30839 msHTTP/1.1Vercel
2https://www.transparency.org/30162 msHTTP/1.1cloudflare
3https://www.transparency.org/en/20073 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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
TLS Certificate Expiry & Recommendations
83 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
B
CDN & Delivery
Vercel
REVIEW
Vercel
Info::
Site is served via Vercel CDN
Got: x-vercel-id: iad1::p9glm-1776816068852-3b3101d1fb94
CDN Detected: Vercel
Provider Vercel Evidence x-vercel-id: iad1::p9glm-1776816068852-3b3101d1fb94
A+
DNS Records
1 A records, 6 ms lookup
PASS
1 A records, 6 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 76.76.21.21
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: dns1.comlaude-dns.com, dns2.comlaude-dns.net, dns3.comlaude-dns.co.uk, dns4.comlaude-dns.eu
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: 6 ms
Got: 6 ms
A76.76.21.21
AAAA—
CNAME—
NSdns1.comlaude-dns.com, dns2.comlaude-dns.net, dns3.comlaude-dns.co.uk, dns4.comlaude-dns.eu
MX
0 transparency-org.mail.protection.outlook.com
TXT
facebook-domain-verification=p7ep7h2o9hcx1a26rchlbwbkfraf5h
google-site-verification=IfYCMmWw-6jD6LhI0Q12-EoiFgkjPFRSjl0wn8DyP4Y
google-site-verification=r25ri6luDo5pEArlLQzgySZ-cLXX8bhplryoKzkn7Uw
pardot853323=af4b8a5b44c38f38056a0f0b45674483bd20fff4c6c33d0f5a2e04cac79a7eda
pardot860503=7b0039eca0c581e4b30e4fe86c9f6a713a440c99557c732b6c34e717358d3eee
google-site-verification=H7cUggoDnI37U5pJmhNmbPo4hUNYh8JIitwu4sy14vY
SPF v=spf1 include:spf.protection.outlook.com include:aspmx.pardot.com include:_spf....
google-site-verification=TRbDHokzV4x8KUEAH5yBBCvj03B4FnPguIf2tn6-qq4
CAALookup not available with standard resolver
Resolved in 6 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
Crawlability
no robots.txt, sitemap with 59 URLs
PASS
no robots.txt, sitemap with 59 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 59 entries
Info::
Sitemap index with 59 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 59 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::
www/non-www redirect configured correctly (preferred: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.transparency.org/
200https://transparency.org/

Preferred variant: non-www

HTTP → HTTPS

308http://transparency.org/ → https://transparency.org/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
transparency.org — via Nom-iq Ltd. dba COM LAUDE, 26 years, 7 months old, hosted on AWS
PASS
transparency.org — via Nom-iq Ltd. dba COM LAUDE, 26 years, 7 months old, hosted on AWS
Info::
Domain registered until Jan 11, 2027 (8 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: Nom-iq Ltd. dba COM LAUDE
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: AWS
Got: AS16509
Domain expiry

212 days

January 11, 2027

SSL certificate

83 days

Issued by Let's Encrypt

Domain age

26 years, 7 months

Registered January 11, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.76.21.21

Registrar

Nom-iq Ltd. dba COM LAUDE

Unlocked 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Nom-iq Ltd. dba COM LAUDE
Created January 11, 2000 (26 years, 7 months ago)
Expires January 11, 2027 (8 months)
Last Updated December 17, 2025
Name Servers dns1.comlaude-dns.com, dns2.comlaude-dns.net, dns3.comlaude-dns.co.uk, dns4.comlaude-dns.eu
DNSSEC Not enabled
Hosting
IP Address 76.76.21.21
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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 74 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 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.
21 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
75 ms
Total Time Total request time from DNS lookup through full response.
75 ms

Connection waterfall

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