Skip to content
https://go.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
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.

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.go.com/
200https://go.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://go.com/ https://www.go.com/

Consistent

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

Certificate validity

134
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
2 A records, 34 ms lookup
PASS
2 A records, 34 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 76.223.18.1, 13.248.150.189
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns1.twdcns.com, ns3.twdcns.info, ns4.twdcns.info, ns6.twdcns.co.uk, ns5.twdcns.co.uk, ns2.twdcns.com
Info::
No MX records — email not configured via DNS
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: 34 ms
Got: 34 ms
A76.223.18.1, 13.248.150.189
AAAA
CNAME
NSns1.twdcns.com, ns3.twdcns.info, ns4.twdcns.info, ns6.twdcns.co.uk, ns5.twdcns.co.uk, ns2.twdcns.com
MX
TXT
htr9iscf127tqthdpuapd75e0s
vn3obnp8on58rh1gbm220mr0o5
34qqnv54o1kpgkan1oefc4chaq
SPF v=spf1 -all
zf4583k7l87r1mb4bn98zl974g3ddrby
6obgql8sf1ebl1h54e4jvd2qqa
CAALookup not available with standard resolver
Resolved in 34 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
Redirect Chain
1 redirect(s), 550 ms total
PASS
1 redirect(s), 550 ms total
Info::
Single redirect
Got: https://go.com → https://www.go.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 550 ms total
Got: 550 ms

https://go.com

422 ms · HTTP/1.1

301

https://www.go.com/

128 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://go.com301422 msHTTP/1.1Apache/2.4.6 (CentOS) PHP/5.4.16
2https://www.go.com/200128 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 212 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 212 B Sitemaps referenced 1 User-agents *, GPTBot, Google-Extended Blocking No — crawling allowed
User-Agent: *
Disallow: /7046/
Disallow: /*?
Disallow: /products/
Disallow: /_xd/
Disallow: /_did/

User-agent: GPTBot
Disallow: /

Sitemap: https://www.go.com/sitemap.xml

User-agent: Google-Extended
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
A+
Domain Intelligence
go.com — via CSC Corporate Domains, Inc., 28 years, 8 months old, hosted on AWS
PASS
go.com — via CSC Corporate Domains, Inc., 28 years, 8 months old, hosted on AWS
Info::
Domain registered until Jan 8, 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: CSC Corporate Domains, Inc.
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

206 days

January 8, 2027

SSL certificate

134 days

Issued by Sectigo Limited

Domain age

28 years, 8 months

Registered January 9, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.248.150.189

Registrar

CSC Corporate Domains, Inc.

Unlocked 6 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 CSC Corporate Domains, Inc.
Created January 9, 1998 (28 years, 8 months ago)
Expires January 8, 2027 (8 months)
Last Updated December 9, 2025
Name Servers ns1.twdcns.com, ns2.twdcns.com, ns3.twdcns.info, ns4.twdcns.info, ns5.twdcns.co.uk, ns6.twdcns.co.uk
DNSSEC Not enabled
Hosting
IP Address 13.248.150.189
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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 448 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
27 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.
314 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
449 ms
Total Time Total request time from DNS lookup through full response.
449 ms

Connection waterfall

DNS Lookup 27 ms TCP Connect 1 ms TLS Handshake 314 ms Server Processing 107 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