Skip to content
https://photobucket.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
99
GRADE
A+
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
7 PASS 2 REVIEW
B
TLS Certificate Expiry & Recommendations
184 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

184
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
B
CDN & Delivery
AWS CloudFront (Error from cloudfront)
REVIEW
AWS CloudFront (Error from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: JFK50-P3)
Got: x-amz-cf-id: nXQe5640yuvUn2gi8EjeL-zTGjwSEo6tWWuIeD9bpQYwllijc7fGAQ==
Info::
CDN cache status: Error from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Error from cloudfront Evidence x-amz-cf-id: nXQe5640yuvUn2gi8EjeL-zTGjwSEo6tWWuIeD9bpQYwllijc7fGAQ==
A+
DNS Records
4 A records, 13 ms lookup
PASS
4 A records, 13 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 108.138.106.5, 108.138.106.44, 108.138.106.110, 108.138.106.111
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:24f0:c600:c:873e:f1c0:93a1, 2600:9000:24f0:1000:c:873e:f1c0:93a1, 2600:9000:24f0:4800:c:873e:f1c0:93a1, 2600:9000:24f0:fe00:c:873e:f1c0:93a1, 2600:9000:24f0:8200:c:873e:f1c0:93a1, 2600:9000:24f0:da00:c:873e:f1c0:93a1, 2600:9000:24f0:d000:c:873e:f1c0:93a1, 2600:9000:24f0:7800:c:873e:f1c0:93a1
Info::
4 nameserver(s) configured
Got: ns-1454.awsdns-53.org, ns-1887.awsdns-43.co.uk, ns-56.awsdns-07.com, ns-930.awsdns-52.net
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: 13 ms
Got: 13 ms
A108.138.106.5, 108.138.106.44, 108.138.106.110, 108.138.106.111
AAAA2600:9000:24f0:c600:c:873e:f1c0:93a1, 2600:9000:24f0:1000:c:873e:f1c0:93a1, 2600:9000:24f0:4800:c:873e:f1c0:93a1, 2600:9000:24f0:fe00:c:873e:f1c0:93a1, 2600:9000:24f0:8200:c:873e:f1c0:93a1, 2600:9000:24f0:da00:c:873e:f1c0:93a1, 2600:9000:24f0:d000:c:873e:f1c0:93a1, 2600:9000:24f0:7800:c:873e:f1c0:93a1
CNAME—
NSns-1454.awsdns-53.org, ns-1887.awsdns-43.co.uk, ns-56.awsdns-07.com, ns-930.awsdns-52.net
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
Validity-Domain-Verification=z/wCHHG/RxLGU9zsFoicNkIIL/0=
_globalsign-domain-verification=BHpWxHhQlVmC0Qh679dy4Ss6Rgh7znn8Rq7XF2qe6V
anthropic-domain-verification-n5etj7=St82ZwiAvLJvsaRlxQHhjxFef
cl3lrb0pqluj4op9vhhjehff7u
dpj383l96u97o.cloudfront.net
facebook-domain-verification=ye4iizahl6yfqef27zxatby4g3j5ct
firebase=photobucket-mobile-apps
globalsign-domain-verification=KaParXxs1OHDy7o8CMbPpHBN-2m_mzwdPqKMMQ66a6
google-site-verification=0cI-SFXYiHgHEb-PSriUKl7X7_jYc9Zw9lmVagsPf5M
google-site-verification=3F-_FrutF1W7ErYlDUGbNkO2o6dcHum3O1YtDiZX19c
google-site-verification=6OHsCGi-QjOlnlyD5RtlTHKewja9BbTHsmZyGTwqD8s
google-site-verification=WJHzJGlUlYXGG4ScPtVCC5qeA8XhCSbrk9xPRMBxpmA
SPF v=spf1 a mx include:_netblocks.google.com include:_netblocks2.google.com include...
yandex-verification: 64da077140896d7b
CAALookup not available with standard resolver
Resolved in 13 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://photobucket.com

https://photobucket.com

23 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://photobucket.com20023 msHTTP/1.1Photobucket
A+
IPv6 Readiness
IPv6 reachable (57 ms)
PASS
IPv6 reachable (57 ms)
Info::
IPv6 is configured and reachable at 2600:9000:24f0:c600:c:873e:f1c0:93a1, 2600:9000:24f0:1000:c:873e:f1c0:93a1, 2600:9000:24f0:4800:c:873e:f1c0:93a1, 2600:9000:24f0:fe00:c:873e:f1c0:93a1, 2600:9000:24f0:8200:c:873e:f1c0:93a1, 2600:9000:24f0:da00:c:873e:f1c0:93a1, 2600:9000:24f0:d000:c:873e:f1c0:93a1, 2600:9000:24f0:7800:c:873e:f1c0:93a1
Got: 57 ms connect
IPv6 Ready
AAAA Records 2600:9000:24f0:c600:c:873e:f1c0:93a1, 2600:9000:24f0:1000:c:873e:f1c0:93a1, 2600:9000:24f0:4800:c:873e:f1c0:93a1, 2600:9000:24f0:fe00:c:873e:f1c0:93a1, 2600:9000:24f0:8200:c:873e:f1c0:93a1, 2600:9000:24f0:da00:c:873e:f1c0:93a1, 2600:9000:24f0:d000:c:873e:f1c0:93a1, 2600:9000:24f0:7800:c:873e:f1c0:93a1 Connection Reachable (57 ms)
A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 492 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 492 B Sitemaps referenced 0 User-agents SemrushBot-SEOAB, Bytespider, PetalBot, *, SemrushBot, SemrushBot-SA, SemrushBot-SI, SemrushBot-SWA, SemrushBot-BA, SemrushBot-CT, SemrushBot-BM Blocking No — crawling allowed
User-agent: *

Disallow: /userprofilehp

Disallow: /u/


User-agent: *

Allow: /


User-agent: SemrushBot

Disallow: /


User-agent: SemrushBot-SA

Disallow: /


User-agent: SemrushBot-BA

Disallow: /


User-agent: SemrushBot-SI

Disallow: /


User-agent: SemrushBot-SWA

Disallow: /


User-agent: SemrushBot-CT

Disallow: /


User-agent: SemrushBot-BM

Disallow: /


User-agent: SemrushBot-SEOAB

Disallow: /


User-agent: Bytespider

Disallow /

User-agent: PetalBot

Disallow /
sitemap.xml 200 OK
Type URL Set URLs 6 entries Valid XML Yes
Sample URLs:
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

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

Preferred variant: non-www

HTTP → HTTPS

301http://photobucket.com/ → https://photobucket.com/

Consistent

A+
Domain Intelligence
photobucket.com — via Amazon Registrar, Inc., 23 years, 3 months old
PASS
photobucket.com — via Amazon Registrar, Inc., 23 years, 3 months old
Info::
Domain registered until May 8, 2027 (1 years 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: Amazon Registrar, 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.
Domain expiry

329 days

May 8, 2027

SSL certificate

184 days

Issued by Amazon

Domain age

23 years, 3 months

Registered May 8, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:9000:24f0:be00:c:873e:f1c0:93a1

Registrar

Amazon Registrar, Inc.

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 Amazon Registrar, Inc.
Created May 8, 2003 (23 years, 3 months ago)
Expires May 8, 2027 (1 years)
Last Updated April 3, 2026
Name Servers ns-1454.awsdns-53.org, ns-1887.awsdns-43.co.uk, ns-56.awsdns-07.com, ns-930.awsdns-52.net
DNSSEC Not enabled
Hosting
IP Address 2600:9000:24f0:be00:c:873e:f1c0:93a1
Data source: rdap (0.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 69 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
12 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.
70 ms
Total Time Total request time from DNS lookup through full response.
70 ms

Connection waterfall

DNS Lookup 12 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 53 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