Skip to content
https://photoshelter.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
76
GRADE
C
FIX
3
REVIEW
2
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 2 REVIEW 3 FIX
D
Redirect Chain
Action
2 redirect(s), 1033 ms total
FIX
2 redirect(s), 1033 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://photoshelter.com to https://www.photoshelter.com
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: http://www.photoshelter.com/
Warning::
Redirect overhead: 1033 ms total
Got: 1033 ms

https://photoshelter.com

313 ms · HTTP/1.1

301

http://www.photoshelter.com/

350 ms · HTTP/1.1

302

https://www.photoshelter.com

370 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://photoshelter.com301313 msHTTP/1.1
2http://www.photoshelter.com/302350 msHTTP/1.1
3https://www.photoshelter.com200370 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

Redirect directly from https://photoshelter.com to https://www.photoshelter.com

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: 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

D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.photoshelter.com/
200https://photoshelter.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://photoshelter.com/ → http://www.photoshelter.com/

HTTP version does not redirect to HTTPS

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
TLS Certificate Expiry & Recommendations
169 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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, 164 ms lookup
PASS
2 A records, 164 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 69.22.188.41, 69.22.188.40
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: a.ns.nyc.bitshelter.com, b.ns.sfo.bitshelter.com, b.ns.nyc.bitshelter.com, a.ns.sfo.bitshelter.com
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: 164 ms
Got: 164 ms
A69.22.188.41, 69.22.188.40
AAAA—
CNAME—
NSa.ns.nyc.bitshelter.com, b.ns.sfo.bitshelter.com, b.ns.nyc.bitshelter.com, a.ns.sfo.bitshelter.com
MX
15 ASPMX.L.GOOGLE.com
20 ALT1.ASPMX.L.GOOGLE.com
20 ALT2.ASPMX.L.GOOGLE.com
30 ALT3.ASPMX.L.GOOGLE.com
40 ALT4.ASPMX.L.GOOGLE.com
TXT
atlassian-domain-verification=ClMF1wYRzIGgvB1yoRT5yYiK0L4xrTQNJ53lahBSmSJ4ketFkR...
SPF v=spf1 ip4:63.141.214.0/23 ip4:69.22.188.0/24 ip4:89.117.31.192/29 ip6:2602:fa85...
google-site-verification=FCnlC1DSrx_VZ22-VmJo3fQLJtTgH21ByQ17VPX36hY
facebook-domain-verification=fe70yfls5pepwq4w6f3za4tguenovi
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+
Crawlability
robots.txt present, sitemap with 73 URLs
PASS
robots.txt present, sitemap with 73 URLs
Info::
robots.txt is present
Got: 1281 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 73 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1281 B Sitemaps referenced 9 User-agents Baiduspider, AhrefsBot, ClaudeBot, *, Riddler, Amazonbot, MJ12bot, Twitterbot, PetalBot Blocking No — crawling allowed
# ROBOTS.TXT FOR PHOTOSHELTER.COM
Sitemap: https://www.photoshelter.com/sitemap-static.xml
Sitemap: https://www.photoshelter.com/users-sitemapindex/0.xml.gz
Sitemap: https://www.photoshelter.com/users-sitemapindex/1.xml.gz
Sitemap: https://www.photoshelter.com/users-sitemapindex/2.xml.gz
Sitemap: https://www.photoshelter.com/users-sitemapindex/3.xml.gz
Sitemap: https://www.photoshelter.com/users-sitemapindex/4.xml.gz
Sitemap: https://www.photoshelter.com/users-sitemapindex/5.xml.gz
Sitemap: https://www.photoshelter.com/users-sitemapindex/6.xml.gz
Sitemap: https://www.photoshelter.com/users-sitemapindex/7.xml.gz

# Was disallowed because it was overly aggressive
# access re-enabled on May 30, 2013
# User-agent: ia_archiver
# Disallow: /

User-agent: *
Disallow: /adm/
Disallow: /ajax/
Disallow: /com/
Disallow: /ext/
Disallow: /ltr/
Disallow: /mem/
Disallow: /mu/
Disallow: /pp/
Disallow: /ezp/
Disallow: /cart/
Disallow: /c/*/login
Disallow: /c/*/signup*
Disallow: /fees
Disallow: /signup/trial

User-agent: MJ12bot
Disallow: 

User-agent: Twitterbot
Disallow:

User-agent: PetalBot
Disallow: /

User-agent: Riddler
Disallow: /

User-agent: Baiduspider
Disallow: /

User-agent: AhrefsBot
Disallow: /

User-agent: Amazonbot
Disallow: /

User-agent: ClaudeBot
Disallow: /
sitemap.xml 200 OK
Type URL Set URLs 73 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
photoshelter.com — via GoDaddy.com, LLC, 21 years, 7 months old, hosted on BITSHELTER-NYC - PhotoShelter, Inc., US
PASS
photoshelter.com — via GoDaddy.com, LLC, 21 years, 7 months old, hosted on BITSHELTER-NYC - PhotoShelter, Inc., US
Info::
Domain registered until Dec 24, 2026 (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: 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: BITSHELTER-NYC - PhotoShelter, Inc., US
Got: AS62804
Domain expiry

193 days

December 24, 2026

SSL certificate

169 days

Issued by DigiCert Inc

Domain age

21 years, 7 months

Registered December 24, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

BITSHELTER-NYC - PhotoShelter, Inc., US

ASN AS62804

69.22.188.40

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 December 24, 2004 (21 years, 7 months ago)
Expires December 24, 2026 (8 months)
Last Updated December 24, 2025
Name Servers a.ns.nyc.bitshelter.com, a.ns.sfo.bitshelter.com, b.ns.nyc.bitshelter.com, b.ns.sfo.bitshelter.com
DNSSEC Not enabled
Hosting
IP Address 69.22.188.40
ASN AS62804 (BITSHELTER-NYC - PhotoShelter, Inc., US)
Provider BITSHELTER-NYC - PhotoShelter, Inc., US
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 396 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
99 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
98 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
100 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
396 ms
Total Time Total request time from DNS lookup through full response.
397 ms

Connection waterfall

DNS Lookup 99 ms TCP Connect 98 ms TLS Handshake 100 ms Server Processing 99 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