Skip to content
https://gigabyte.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 5 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
1 redirect(s), 1132 ms total
REVIEW
1 redirect(s), 1132 ms total
Info::
Single redirect
Got: https://gigabyte.com → https://www.gigabyte.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1132 ms total
Got: 1132 ms

https://gigabyte.com

1034 ms · HTTP/1.1

301

https://www.gigabyte.com/

98 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gigabyte.com3011034 msHTTP/1.1nginx
2https://www.gigabyte.com/40398 msHTTP/1.1

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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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 No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 1126 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
267 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
547 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.13 s
Total Time Total request time from DNS lookup through full response.
1.13 s

Connection waterfall

DNS Lookup 38 ms TCP Connect 267 ms TLS Handshake 547 ms Server Processing 274 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
178 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

178
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
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
1 A records, 54 ms lookup
PASS
1 A records, 54 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 103.130.100.144
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: ns0226.secondary.cloudflare.com, ns0061.secondary.cloudflare.com
Info::
2 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: 54 ms
Got: 54 ms
A103.130.100.144
AAAA
CNAME
NSns0226.secondary.cloudflare.com, ns0061.secondary.cloudflare.com
MX
5 ppsmx1.gigabyte.com
10 ppsmx2.gigabyte.com
TXT
3a5pM5esJ7a1mf7P4Dl13Ox8EP9+IdPIGo0HaezEcQoP/ZS7nqXjzFVRmVTLlA0TMdHMjMUc6CNX105i...
SPF v=spf1 include:spf.protection.outlook.com include:_spf1.gigabyte.com include:spf...
Bz2EV-Njo1hU-IWxCRcBOwS90XvDcJ-E0VyrCF8yhbY
WOLiaiw5vHMJBtKsMhjT_ENfjA-PctfzQOteAIiQLoE
MS=ms57490047
google-site-verification=7MQXeVsdWG-vo41NvtF2RCG_UF7d4FsaLAECKN1O-xI
knowbe4-site-verification=4a326c61c4ee6f04e466fe6025ac5c32
vxua6amOEDPxqkBpZTdeKC1+yWTt4c9WOfYs3tXd5s8uwj7dVxFikPbQPxq5/pGXRHYhBTr6QQrQC03H...
hcBBc9U161wfNhWheR0tSFy8YZHjrs__TFvenUOoR2o
sophos-domain-verification=a510856a3ffe21976e4ffa2358e4a800a6279fb2387d52a5fa2e8...
duo_sso_verification=FIxoMRN7qtQx2T0HnpoMXcHuhIyh5lDGErYYZwPtfL9Bp6ajdD8raiOPfpC...
google-gws-recovery-domain-verification=49768321
wombat-verification=3KwxVCQV1HEp-aRXRTKKaZ5G0frhk
MS=ms14271882
58e02982efb23d66cb7d1eacd1e5813d8761470da1ae78c38aed6dc29690bdc8
KA2nc4fOF8NwZgjmH5SIX8TY9EE2rXE1YYd2qDFeL3A
CAALookup not available with standard resolver
Resolved in 54 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

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+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.gigabyte.com/
200https://gigabyte.com/

HTTP → HTTPS

301http://gigabyte.com/ https://gigabyte.com/

Consistent

A+
Domain Intelligence
gigabyte.com — via CSC Corporate Domains, Inc., 29 years, 7 months old, hosted on GIGABYTE-AS-TW GIGABYTE, TW
PASS
gigabyte.com — via CSC Corporate Domains, Inc., 29 years, 7 months old, hosted on GIGABYTE-AS-TW GIGABYTE, TW
Info::
Domain registered until Feb 12, 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: 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: GIGABYTE-AS-TW GIGABYTE, TW
Got: AS131663
Domain expiry

179 days

February 12, 2027

SSL certificate

178 days

Issued by TAIWAN-CA

Domain age

29 years, 7 months

Registered February 11, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

GIGABYTE-AS-TW GIGABYTE, TW

ASN AS131663

103.130.100.144

Registrar

CSC Corporate Domains, Inc.

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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created February 11, 1997 (29 years, 7 months ago)
Expires February 12, 2027 (9 months)
Last Updated February 8, 2026
Name Servers ns0061.secondary.cloudflare.com, ns0226.secondary.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 103.130.100.144
ASN AS131663 (GIGABYTE-AS-TW GIGABYTE, TW)
Provider GIGABYTE-AS-TW GIGABYTE, TW
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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback