Skip to content
https://sprytal.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
7 PASS 8 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 273ms across 3 resolvers (spread 433ms)
FIX
Mean 273ms across 3 resolvers (spread 433ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Google: 382ms
Got: 382ms via 8.8.8.8:53
Info::
Quad9: 435ms
Got: 435ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 433ms (min 2ms / max 435ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
D
HTTP Probe Timing
Action
Total 2581 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
491 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
250 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
255 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
2.33 s
Total Time Total request time from DNS lookup through full response.
2.58 s

Connection waterfall

DNS Lookup 491 ms TCP Connect 250 ms TLS Handshake 255 ms Server Processing 1.33 s Content Transfer 251 ms
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 66.116.229.214 does not match any cert SAN: 66-116-229-214.unifiedlayer.com
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
TLS Certificate Expiry & Recommendations
37 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
C
CDN & Delivery
Action
Assets on Cloudflare (host cdnjs.cloudflare.com, 4 assets); document served directly from origin (Oracle Cloud)
REVIEW
Assets on Cloudflare (host cdnjs.cloudflare.com, 4 assets); document served directly from origin (Oracle Cloud)
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (cdnjs.cloudflare.com, 4 assets), but the HTML document itself comes straight from the origin (Oracle Cloud). Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: cf-ray: a49757726cb58bf6-GRU
Info::
Assets on Cloudflare: cdnjs.cloudflare.com (assets: 4), cache BYPASS
Got: cf-ray: a49757726cb58bf6-GRU
Warning: Assets on a CDN, document is not: Cloudflare
Document origin Oracle Cloud

Asset hosts on a CDN

  • cdnjs.cloudflare.com — Cloudflare · assets: 4 · Cache Status: BYPASS

Other asset hosts

  • fonts.googleapis.com — assets: 4 · Google
  • chatzy-kb-store.s3.amazonaws.com — assets: 3 · AWS
  • www.googletagmanager.com — assets: 2 · below probe threshold
  • www.google.com — assets: 1 · below probe threshold
  • www.gstatic.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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.
A
DNS Records
1 A records, 527 ms lookup
PASS
1 A records, 527 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 66.116.229.214
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: sns00034.bigrock.com, sns00033.bigrock.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (527 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 527 ms
A66.116.229.214
AAAA—
CNAME—
NSsns00034.bigrock.com, sns00033.bigrock.com
MX
10 mx1.titan.email
TXT
SPF v=spf1 include:spf.titan.email ~all
google-site-verification=TC8UoTPX4S02feY_kkar0mthWH-K9NR0AyJH3uWKS7w
CAALookup not available with standard resolver
Resolved in 527 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://sprytal.com

https://sprytal.com

1264 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://sprytal.com2001264 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 10 URLs
PASS
robots.txt present, sitemap with 10 URLs
Info::
robots.txt is present
Got: 914 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 10 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 914 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# If the Joomla site is installed within a folder

# eg www.example.com/joomla/ then the robots.txt file

# MUST be moved to the site root

# eg www.example.com/robots.txt

# AND the joomla folder name MUST be prefixed to all of the

# paths.

# eg the Disallow rule for the /administrator/ folder MUST

# be changed to read

# Disallow: /joomla/administrator/

#

# For more information about the robots.txt standard, see:

# https://www.robotstxt.org/orig.html


User-agent: *

Allow: /*.js*

Allow: /*.css*

Allow: /*.png*

Allow: /*.jpg*

Allow: /*.gif*


Disallow: /administrator/

Disallow: /api/

Disallow: /bin/

Disallow: /cache/

Disallow: /cli/


Disallow: /includes/

Disallow: /installation/

Disallow: /language/

Disallow: /layouts/

Disallow: /libraries/

Disallow: /logs/



Disallow: /tmp/


# JSitemap entries

Sitemap: https://sprytal.com/index.php?option=com_jmap&view=sitemap&format=xml
sitemap.xml 200 OK
Type URL Set URLs 10 entries Valid XML Yes
Sample URLs:
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.sprytal.com/
200https://sprytal.com/

Preferred variant: non-www

HTTP → HTTPS

301http://sprytal.com/ → https://sprytal.com/

Consistent

A+
Domain Intelligence
sprytal.com — via BigRock Solutions Ltd, 1 months old, hosted on Oracle Cloud
PASS
sprytal.com — via BigRock Solutions Ltd, 1 months old, hosted on Oracle Cloud
Info::
Domain registered until Aug 21, 2027 (10 months remaining)
Info::
Domain is only 1 months old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Aug 21, 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: BigRock Solutions Ltd
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: Oracle Cloud
Got: AS31898
Domain expiry

306 days

August 21, 2027

SSL certificate

37 days

Issued by Let's Encrypt

Domain age

1 months

Registered August 21, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Oracle Cloud

ASN AS31898

66.116.229.214

Registrar

BigRock Solutions Ltd

Unlocked 2 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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar BigRock Solutions Ltd
Created August 21, 2026 (1 months ago)
Expires August 21, 2027 (10 months)
Last Updated August 21, 2026
Name Servers sns00033.bigrock.com, sns00034.bigrock.com
DNSSEC Not enabled
Hosting
IP Address 66.116.229.214
ASN AS31898 (ORACLE-BMC-31898 - Oracle Corporation, US)
Provider Oracle Cloud
Data source: rdap (1.4s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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+
Health Check Endpoint
Health endpoint at https://sprytal.com/health (HTTP 200)
PASS
Health endpoint at https://sprytal.com/health (HTTP 200)
Info::
Public health endpoint at https://sprytal.com/health
Got: https://sprytal.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback