Skip to content
https://imageshack.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
6
PASS
3
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
3 PASS 6 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 2517 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2517 B Sitemaps referenced 0 User-agents Amazonbot, Bytespider, ChatGPT Agent, Google-CloudVertexBot, Google-Extended, OAI-SearchBot, PerplexityBot, PetalBot, Datenbank Crawler, FriendlyCrawler, MistralAI-User, Operator, quillbot.com, SBIntuitionsBot, YandexAdditionalBot, meta-externalfetcher, aiHitBot, bigsur.ai, Cotoyogi, GPTBot, ISSCyberRiskCrawler, PanguBot, Webzio-Extended, AI2Bot, ChatGPT-User, Gemini-Deep-Research, omgili, PhindBot, Claude-User, CloudVertexBot, MyCentralAIScraperBot, Scrapy, Awario, ClaudeBot, Crawlspace, facebookexternalhit, ICC-Crawler, YaK, Ai2Bot-Dolma, ImagesiftBot, Meta-ExternalAgent, Meta-ExternalFetcher, netEstate Imprint Crawler, OpenAI, VelenPublicWebCrawler, wpbot, Google-Firebase, Panscient, Perplexity-User, Thinkbot, TikTokSpider, AddSearchBot, cohere-ai, QualifiedBot, SemrushBot-OCOB, SemrushBot-SWA, Timpibot, *, anthropic-ai, Applebot, Claude-SearchBot, Devin, iaskspider/2.0, meta-externalagent, omgilibot, QuillBot, Brightbot 1.0, Echobot Bot, GoogleOther-Image, NovaAct, panscient.com, Poseidon Research Crawler, ShapBot, YandexAdditional, Applebot-Extended, Claude-Web, cohere-training-data-crawler, GoogleOther-Video, MistralAI-User/1.0, WARDBot, YouBot, CCBot, Diffbot, meta-webindexer, bedrockbot, DuckAssistBot, FacebookBot, GoogleAgent-Mariner, img2dataset, Kangaroo Bot, Sidetrade indexer bot, Andibot, EchoboxBot, FirecrawlAgent, LinerBot, Factset_spyderbot, GoogleOther, TerraCotta Blocking No — crawling allowed
User-agent: AddSearchBot
User-agent: AI2Bot
User-agent: Ai2Bot-Dolma
User-agent: aiHitBot
User-agent: Amazonbot
User-agent: Andibot
User-agent: anthropic-ai
User-agent: Applebot
User-agent: Applebot-Extended
User-agent: Awario
User-agent: bedrockbot
User-agent: bigsur.ai
User-agent: Brightbot 1.0
User-agent: Bytespider
User-agent: CCBot
User-agent: ChatGPT Agent
User-agent: ChatGPT-User
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: Claude-Web
User-agent: ClaudeBot
User-agent: CloudVertexBot
User-agent: cohere-ai
User-agent: cohere-training-data-crawler
User-agent: Cotoyogi
User-agent: Crawlspace
User-agent: Datenbank Crawler
User-agent: Devin
User-agent: Diffbot
User-agent: DuckAssistBot
User-agent: Echobot Bot
User-agent: EchoboxBot
User-agent: FacebookBot
User-agent: facebookexternalhit
User-agent: Factset_spyderbot
User-agent: FirecrawlAgent
User-agent: FriendlyCrawler
User-agent: Gemini-Deep-Research
User-agent: Google-CloudVertexBot
User-agent: Google-Extended
User-agent: Google-Firebase
User-agent: GoogleAgent-Mariner
User-agent: GoogleOther
User-agent: GoogleOther-Image
User-agent: GoogleOther-Video
User-agent: GPTBot
User-agent: iaskspider/2.0
User-agent: ICC-Crawler
User-agent: ImagesiftBot
User-agent: img2dataset
User-agent: ISSCyberRiskCrawler
User-agent: Kangaroo Bot
User-agent: LinerBot
User-agent: meta-externalagent
User-agent: Meta-ExternalAgent
User-agent: meta-externalfetcher
User-agent: Meta-ExternalFetcher
User-agent: meta-webindexer
User-agent: MistralAI-User
User-agent: MistralAI-User/1.0
User-agent: MyCentralAIScraperBot
User-agent: netEstate Imprint Crawler
User-agent: NovaAct
User-agent: OAI-SearchBot
User-agent: omgili
User-agent: omgilibot
User-agent: OpenAI
User-agent: Operator
User-agent: PanguBot
User-agent: Panscient
User-agent: panscient.com
User-agent: Perplexity-User
User-agent: PerplexityBot
User-agent: PetalBot
User-agent: PhindBot
User-agent: Poseidon Research Crawler
User-agent: QualifiedBot
User-agent: QuillBot
User-agent: quillbot.com
User-agent: SBIntuitionsBot
User-agent: Scrapy
User-agent: SemrushBot-OCOB
User-agent: SemrushBot-SWA
User-agent: ShapBot
User-agent: Sidetrade indexer bot
User-agent: TerraCotta
User-agent: Thinkbot
User-agent: TikTokSpider
User-agent: Timpibot
User-agent: VelenPublicWebCrawler
User-agent: WARDBot
User-agent: Webzio-Extended
User-agent: wpbot
User-agent: YaK
User-agent: YandexAdditional
User-agent: YandexAdditionalBot
User-agent: YouBot
Disallow: /

User-agent: *
Disallow: /download/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

200http://imageshack.com/

HTTP version does not redirect to HTTPS

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

Connection waterfall

DNS Lookup 164 ms TCP Connect 146 ms TLS Handshake 442 ms Server Processing 148 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
320 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

320
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
B
CDN & Delivery
Varnish
REVIEW
Varnish
Info::
Site is served via Varnish CDN
Got: via: 1.1 varnish
CDN Detected: Varnish
Provider Varnish Evidence via: 1.1 varnish
A+
DNS Records
2 A records, 164 ms lookup
PASS
2 A records, 164 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 208.94.3.17, 208.94.3.16
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns5.imageshack.us, ns2.imageshack.us, ns4.imageshack.us, ns3.imageshack.us
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: 164 ms
Got: 164 ms
A208.94.3.17, 208.94.3.16
AAAA—
CNAME—
NSns5.imageshack.us, ns2.imageshack.us, ns4.imageshack.us, ns3.imageshack.us
MX
10 ASPMX.L.GOOGLE.com
20 ALT2.ASPMX.L.GOOGLE.com
20 ALT1.ASPMX.L.GOOGLE.com
30 ASPMX3.GOOGLEMAIL.com
30 ASPMX4.GOOGLEMAIL.com
30 ASPMX5.GOOGLEMAIL.com
30 ASPMX2.GOOGLEMAIL.com
TXT
google-site-verification=vT6fb2R4XxzNnsByIczW4Q7lt3Pug2eYrbShPLd4zrE
SPF v=spf1 ip4:208.94.0.68 ip4:208.94.0.103 include:_spf.google.com ~all exp=diag.sp...
Use of content under this domain in AI technologies is subject to the licensing ...
google-site-verification=oIco_ftb8BU2xHaJ48CwjziXfvPGt3wQMkCupdDjpxM
google-site-verification=_UGU9JQAf1954qC5QPZ_XUQcUaasByN8fCQil9h37kA
CAALookup not available with standard resolver
Resolved in 164 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://imageshack.com

https://imageshack.com

738 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://imageshack.com200738 msHTTP/1.1nginx/1.2.8
A+
Domain Intelligence
imageshack.com — via GoDaddy.com, LLC, 24 years old, hosted on EZRI-36323 - Ezri Inc, US
PASS
imageshack.com — via GoDaddy.com, LLC, 24 years old, hosted on EZRI-36323 - Ezri Inc, US
Info::
Domain registered until Aug 11, 2028 (2 years, 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: GoDaddy.com, 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: EZRI-36323 - Ezri Inc, US
Got: AS36323
Domain expiry

788 days

August 11, 2028

SSL certificate

320 days

Issued by GoDaddy.com, Inc.

Domain age

24 years

Registered August 11, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

EZRI-36323 - Ezri Inc, US

ASN AS36323

208.94.3.16

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created August 11, 2002 (24 years ago)
Expires August 11, 2028 (2 years, 4 months)
Last Updated August 12, 2023
Name Servers ns2.imageshack.us, ns3.imageshack.us, ns4.imageshack.us, ns5.imageshack.us
DNSSEC Not enabled
Hosting
IP Address 208.94.3.16
ASN AS36323 (EZRI-36323 - Ezri Inc, US)
Provider EZRI-36323 - Ezri Inc, US
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

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

Send Feedback