Skip to content
https://banktrack.org

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
17
7 PASS 9 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
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Multi-Resolver DNS Speed
Mean 106ms across 3 resolvers (spread 156ms)
REVIEW
Mean 106ms across 3 resolvers (spread 156ms)
Info::
Google: 10ms
Got: 10ms via 8.8.8.8:53
Info::
Cloudflare: 144ms
Got: 144ms via 1.1.1.1:53
Info::
Quad9: 166ms
Got: 166ms via 9.9.9.9:53
B
Redirect Chain
1 redirect(s), 2188 ms total
REVIEW
1 redirect(s), 2188 ms total
Info::
Single redirect
Got: https://banktrack.org → https://www.banktrack.org/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2188 ms total
Got: 2188 ms

https://banktrack.org

878 ms · HTTP/1.1

301

https://www.banktrack.org/

1311 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://banktrack.org301878 msHTTP/1.1Apache
2https://www.banktrack.org/2001311 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://banktrack.org/ → https://www.banktrack.org/

Consistent

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

Certificate validity

61
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 Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
1 A records, 438 ms lookup
PASS
1 A records, 438 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 149.210.144.80
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: ns0.transip.net, ns1.transip.nl, ns2.transip.eu
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (438 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 438 ms
A149.210.144.80
AAAA—
CNAME—
NSns0.transip.net, ns1.transip.nl, ns2.transip.eu
MX
1 ASPMX.L.GOOGLE.COM
5 ALT1.ASPMX.L.GOOGLE.COM
5 ALT2.ASPMX.L.GOOGLE.COM
10 ALT3.ASPMX.L.GOOGLE.COM
10 ALT4.ASPMX.L.GOOGLE.COM
TXT
MS=ms37148128
SPF v=spf1 ip4:149.210.144.80 include:_spf.google.com -all
google-site-verification=cc3XkYr5p-qhT_fkq92PJ282oVG3GLc4vP-Fe1Xq68A
CAALookup not available with standard resolver
Resolved in 438 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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A+
Reverse DNS
1/1 IPs match cert SAN
PASS
1/1 IPs match cert SAN
Info::
PTR for 149.210.144.80 matches certificate SAN: banktrack.org
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 177 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references 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

robots.txt 200 OK
Size 177 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /private

Disallow: /uod

Disallow: /doc

Disallow: /site2011


User-Agent: *

Crawl-Delay: 10

Sitemap: http://www.banktrack.org/sitemap/sitemap.xml
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
Domain Intelligence
banktrack.org — via Key-Systems GmbH, 23 years old, hosted on TRANSIP-AS - Signet B.V., NL
PASS
banktrack.org — via Key-Systems GmbH, 23 years old, hosted on TRANSIP-AS - Signet B.V., NL
Info::
Domain registered until Dec 8, 2026 (3 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Key-Systems GmbH
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: TRANSIP-AS - Signet B.V., NL
Got: AS20857
Domain expiry

113 days

December 8, 2026

SSL certificate

61 days

Issued by Let's Encrypt

Domain age

23 years

Registered December 8, 2003

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

TRANSIP-AS - Signet B.V., NL

ASN AS20857

149.210.144.80

Registrar

Key-Systems GmbH

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Key-Systems GmbH
Created December 8, 2003 (23 years ago)
Expires December 8, 2026 (3 months)
Last Updated August 11, 2026
Name Servers ns0.transip.net, ns1.transip.nl, ns2.transip.eu
DNSSEC Enabled
Hosting
IP Address 149.210.144.80
ASN AS20857 (TRANSIP-AS - Signet B.V., NL)
Provider TRANSIP-AS - Signet B.V., NL
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 293 ms TCP Connect 141 ms TLS Handshake 146 ms Server Processing 142 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