Skip to content
https://goal.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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
Redirect Chain
2 redirect(s), 220 ms total
REVIEW
2 redirect(s), 220 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
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.goal.com:443/

https://goal.com

146 ms · HTTP/1.1

301

https://www.goal.com:443/

70 ms · HTTP/1.1

302

https://www.goal.com/es

4 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://goal.com301146 msHTTP/1.1awselb/2.0
2https://www.goal.com:443/30270 msHTTP/1.1
3https://www.goal.com/es2004 msHTTP/1.1

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

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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
225 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A+
DNS Records
3 A records, 38 ms lookup
PASS
3 A records, 38 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 34.241.121.96, 52.214.150.61, 54.247.119.154
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1803.awsdns-33.co.uk, ns-971.awsdns-57.net, ns-484.awsdns-60.com, ns-1409.awsdns-48.org
Info::
5 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: 38 ms
Got: 38 ms
A34.241.121.96, 52.214.150.61, 54.247.119.154
AAAA—
CNAME—
NSns-1803.awsdns-33.co.uk, ns-971.awsdns-57.net, ns-484.awsdns-60.com, ns-1409.awsdns-48.org
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
tollbit-domain-verification=560eb5b46f8c3b921498b533969d7734e2530dc1785de9ac716e...
klaviyo-site-verification=VYBQby
3E47297E4F
MS=ms66107762
cfqwrhfjdxmn6r9nrfqmhnp1h709m3qn
firebase=goal-live-scores-438bc
SPF v=spf1 include:_spf.google.com include:_spf.firebasemail.com -all
MS=ms18685212
google-site-verification=jUFSt2GRHHOQ2jNVgQO1twiiBZNEdMJsB7MK9Dwmn7w
wzh66szlrcmprkh9jpf26mbl4y3pchmg
google-site-verification=YtB2aT0v9TMyLG57QqeX39b3zVwBnefTNgOv_k8hxfI
4cny8p8zkx7tzgnhbjkqy5rlzjxpxksr
firebase=goal-app-31435
firebase=goal-news-77a5c
openai-domain-verification=dv-tbM3K98AKAFuKYnwJSN9AqsG
CAALookup not available with standard resolver
Resolved in 38 ms

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
robots.txt present, sitemap with 35 URLs
PASS
robots.txt present, sitemap with 35 URLs
Info::
robots.txt is present
Got: 1558 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 35 entries
Info::
Sitemap index with 35 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1558 B Sitemaps referenced 36 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Sitemap: https://www.goal.com/sitemap
Sitemap: https://www.goal.com/ar/sitemap
Sitemap: https://www.goal.com/ar-eg/sitemap
Sitemap: https://www.goal.com/ar-sa/sitemap
Sitemap: https://www.goal.com/br/sitemap
Sitemap: https://www.goal.com/de/sitemap
Sitemap: https://www.goal.com/en/sitemap
Sitemap: https://www.goal.com/en-ae/sitemap
Sitemap: https://www.goal.com/en-au/sitemap
Sitemap: https://www.goal.com/en-ca/sitemap
Sitemap: https://www.goal.com/en-gb/sitemap
Sitemap: https://www.goal.com/en-gh/sitemap
Sitemap: https://www.goal.com/en-in/sitemap
Sitemap: https://www.goal.com/en-ke/sitemap
Sitemap: https://www.goal.com/en-my/sitemap
Sitemap: https://www.goal.com/en-ng/sitemap
Sitemap: https://www.goal.com/en-om/sitemap
Sitemap: https://www.goal.com/en-qa/sitemap
Sitemap: https://www.goal.com/en-sa/sitemap
Sitemap: https://www.goal.com/en-sg/sitemap
Sitemap: https://www.goal.com/en-ug/sitemap
Sitemap: https://www.goal.com/en-us/sitemap
Sitemap: https://www.goal.com/en-za/sitemap
Sitemap: https://www.goal.com/es/sitemap
Sitemap: https://www.goal.com/es-ar/sitemap
Sitemap: https://www.goal.com/es-cl/sitemap
Sitemap: https://www.goal.com/es-mx/sitemap
Sitemap: https://www.goal.com/fr/sitemap
Sitemap: https://www.goal.com/hu/sitemap
Sitemap: https://www.goal.com/id/sitemap
Sitemap: https://www.goal.com/it/sitemap
Sitemap: https://www.goal.com/jp/sitemap
Sitemap: https://www.goal.com/kr/sitemap
Sitemap: https://www.goal.com/th/sitemap
Sitemap: https://www.goal.com/tr/sitemap
Sitemap: https://www.goal.com/vn/sitemap
sitemap.xml 200 OK
Type Sitemap Index URLs 35 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)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.goal.com/
200https://goal.com/

Preferred variant: non-www

HTTP → HTTPS

301http://goal.com/ → https://goal.com:443/

Consistent

A+
Domain Intelligence
goal.com — via SafeNames Ltd., 31 years, 5 months old, hosted on AWS
PASS
goal.com — via SafeNames Ltd., 31 years, 5 months old, hosted on AWS
Info::
Domain registered until Apr 19, 2027 (1 years 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: SafeNames 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: AWS
Got: AS16509
Domain expiry

275 days

April 19, 2027

SSL certificate

225 days

Issued by Amazon

Domain age

31 years, 5 months

Registered April 18, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

54.247.119.154

Registrar

SafeNames Ltd.

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 SafeNames Ltd.
Created April 18, 1995 (31 years, 5 months ago)
Expires April 19, 2027 (1 years)
Last Updated April 19, 2026
Name Servers ns-1409.awsdns-48.org, ns-1803.awsdns-33.co.uk, ns-484.awsdns-60.com, ns-971.awsdns-57.net
DNSSEC Not enabled
Hosting
IP Address 54.247.119.154
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 29 ms TCP Connect 36 ms TLS Handshake 75 ms Server Processing 37 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