Skip to content
https://gyazo.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
9
6 PASS 3 REVIEW
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
154 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
A+
DNS Records
1 A records, 4 ms lookup
PASS
1 A records, 4 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 35.186.213.112
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: gail.ns.cloudflare.com, tom.ns.cloudflare.com
Info::
7 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: 4 ms
Got: 4 ms
A35.186.213.112
AAAA
CNAME
NSgail.ns.cloudflare.com, tom.ns.cloudflare.com
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 aspmx2.googlemail.com
50 aspmx3.googlemail.com
60 aspmx4.googlemail.com
70 aspmx5.googlemail.com
TXT
google-site-verification=0O5ExgzDwCAWIP2ndGd9R9dAeisu5Kqm4qlgoIeSH6o
google-site-verification=1-rEGMas8BVZcQ89eDY4tt6XnnUjm7iBxisVO8R-KQg
google-site-verification=tEhpX_Hi7UAGPanXgNqrUKht-YOySIEsA-d-2yju1AQ
google-site-verification=tvycmFis2wn5ZoY9aNnodHXhQXwVOE_TUfZPoGTDfNQ
SPF v=spf1 include:_spf.google.com include:sendgrid.net include:mail.zendesk.com -al...
CAALookup not available with standard resolver
Resolved in 4 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://gyazo.com

https://gyazo.com

259 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gyazo.com200259 msHTTP/1.1nginx/1.28.0
A+
Crawlability
robots.txt present, sitemap with 21 URLs
PASS
robots.txt present, sitemap with 21 URLs
Info::
robots.txt is present
Got: 62 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 21 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 62 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Sitemap: https://gyazo.com/sitemap.xml

sitemap.xml 200 OK
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.gyazo.com/
200https://gyazo.com/

Preferred variant: non-www

HTTP → HTTPS

301http://gyazo.com/ https://gyazo.com/

Consistent

A+
Domain Intelligence
gyazo.com — via eNom, LLC, 18 years, 10 months old, hosted on Google Cloud
PASS
gyazo.com — via eNom, LLC, 18 years, 10 months old, hosted on Google Cloud
Info::
Domain registered until Aug 31, 2026 (4 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: eNom, 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: Google Cloud
Got: AS396982
Domain expiry

77 days

August 31, 2026

SSL certificate

154 days

Issued by DigiCert Inc

Domain age

18 years, 10 months

Registered August 31, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

35.186.213.112

Registrar

eNom, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar eNom, LLC
Created August 31, 2007 (18 years, 10 months ago)
Expires August 31, 2026 (4 months)
Last Updated August 1, 2025
Name Servers gail.ns.cloudflare.com, tom.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 35.186.213.112
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: rdap (1.0s)

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 287 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 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.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
286 ms
Total Time Total request time from DNS lookup through full response.
287 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 277 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback