Skip to content
https://usatf.org

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
17
8 PASS 9 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
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
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 192.124.249.110 does not match any cert SAN: cloudproxy10010.sucuri.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.usatf.org/
200https://usatf.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Renew certificate — 30 days remaining
  • 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
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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A+
DNS Records
1 A records, 74 ms lookup
PASS
1 A records, 74 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.124.249.110
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns28.worldnic.com, ns27.worldnic.com
Info::
6 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 74 ms
Got: 74 ms
A192.124.249.110
AAAA—
CNAME—
NSns28.worldnic.com, ns27.worldnic.com
MX
10 usatf-org.mail.protection.outlook.com
20 aspmx.l.google.com
30 alt1.aspmx.l.google.com
40 alt2.aspmx.l.google.com
50 aspmx2.googlemail.com
60 aspmx3.googlemail.com
TXT
52i0inulholn8bhipepj132c4i
facebook-domain-verification=af3sys77em94gcvvrc67vuda9wlldu
SPF v=spf1 include:spf.protection.outlook.com include:spf.mandrillapp.com -all
apple-domain-verification=mCEHt1RDWeL9hNvh
dropbox-domain-verification=vi97schbh61g
qmn62lstq0mniadrc82uesi2ba
CAALookup not available with standard resolver
Resolved in 74 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 27ms across 3 resolvers (spread 33ms)
PASS
Mean 27ms across 3 resolvers (spread 33ms)
Info::
Google: 10ms
Got: 10ms via 8.8.8.8:53
Info::
Cloudflare: 28ms
Got: 28ms via 1.1.1.1:53
Info::
Quad9: 43ms
Got: 43ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 351 ms total
PASS
1 redirect(s), 351 ms total
Info::
Single redirect
Got: https://usatf.org → https://www.usatf.org/ (301)
Info::
WWW normalization redirect

https://usatf.org

22 ms · HTTP/1.1

301

https://www.usatf.org/

329 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://usatf.org30122 msHTTP/1.1Sucuri/Cloudproxy
2https://www.usatf.org/200329 msHTTP/1.1Sucuri/Cloudproxy

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 3885 URLs
PASS
robots.txt present, sitemap with 3885 URLs
Info::
robots.txt is present
Got: 96 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3885 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 96 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
user-agent:*

Sitemap: https://usatf.org/sitemap.xml

Disallow: /admin

Disallow: /cmsdesk
sitemap.xml 200 OK
Type URL Set URLs 3885 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
usatf.org — via Network Solutions, LLC, 31 years, 8 months old, hosted on SUCURI-SEC - Sucuri, US
PASS
usatf.org — via Network Solutions, LLC, 31 years, 8 months old, hosted on SUCURI-SEC - Sucuri, US
Info::
Domain registered until Jun 3, 2027 (9 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: Network Solutions, LLC
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: SUCURI-SEC - Sucuri, US
Got: AS30148
Domain expiry

278 days

June 3, 2027

SSL certificate

30 days

Issued by Starfield Technologies

Domain age

31 years, 8 months

Registered June 4, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SUCURI-SEC - Sucuri, US

ASN AS30148

192.124.249.110

Registrar

Network Solutions, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • 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 Network Solutions, LLC
Created June 4, 1995 (31 years, 8 months ago)
Expires June 3, 2027 (9 months)
Last Updated August 12, 2026
Name Servers ns27.worldnic.com, ns28.worldnic.com
DNSSEC Not enabled
Hosting
IP Address 192.124.249.110
ASN AS30148 (SUCURI-SEC - Sucuri, US)
Provider SUCURI-SEC - Sucuri, US
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

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

Connection waterfall

DNS Lookup 28 ms TCP Connect 2 ms TLS Handshake 5 ms Server Processing 3 ms Content Transfer 0 ms
A+
CDN & Delivery
Sucuri (HIT)
PASS
Sucuri (HIT)
Info::
Site is served via Sucuri CDN
Got: x-sucuri-id: 11007
Info::
CDN cache status: HIT
CDN Detected: Sucuri
Provider Sucuri Cache Status HIT Evidence x-sucuri-id: 11007
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback