Skip to content
https://500px.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 100 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 100 B Sitemaps referenced 0 User-agents Googlebot, sitebot, Yeti Blocking No — crawling allowed
User-agent: Googlebot 
Disallow: /g/

User-agent: sitebot
Disallow: /

User-agent: Yeti
Disallow: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
137 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

137
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
4 A records, 113 ms lookup
PASS
4 A records, 113 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 65.8.202.74, 65.8.202.63, 65.8.202.17, 65.8.202.41
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-46.awsdns-05.com, ns-1489.awsdns-58.org, ns-557.awsdns-05.net, ns-1537.awsdns-00.co.uk
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: 113 ms
Got: 113 ms
A65.8.202.74, 65.8.202.63, 65.8.202.17, 65.8.202.41
AAAA
CNAME
NSns-46.awsdns-05.com, ns-1489.awsdns-58.org, ns-557.awsdns-05.net, ns-1537.awsdns-00.co.uk
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
TXT
globalsign-domain-verification=qhllLTVNbc63_k7N_0u2VjkgHnq48qKQ8gKVvHWkHI
google-site-verification=S04RaTFPqq4HltajpzefbpO70i_upGV0K_ouOO0OxQQ
google-site-verification=rsN2pQDJmMMbvmHgxrwAMxYlZZkxvmRB_tUXYst1KWs
_globalsign-domain-verification=95YZs-Lq6mpDrrS5bnsvxSp8Llz8ZsgkwBGGx8RQVh
_globalsign-domain-verification=-awtonA3izZim7M9dNMwrH07WjvKC5se353wYCAliP
google-site-verification=ZgRM2rlVyygnVx8LKAHjlIJiiBZo-nNg1NwxVwfxC8Y
google-site-verification=HN8EFqOttE0aHSUCuiG34qND9uEUM-PsE4CggywJJQ8
SPF v=spf1 include:_spf.google.com include:_spf.500px.com include:spf.tipalti.com in...
spycloud-domain-verification=ad20fc6e-08f9-4e09-9780-9a22f5c6766c
_globalsign-domain-verification=9UioyPO0_F2Epyd3gGV5_VklXzoibTukD_jkbZPw43
atlassian-domain-verification=18NPrx3jAHcYPT76x92Y3qxWpldkm+07OR+QrdH5R6ExBKZkkq...
google-site-verification=Yfbh7eK9kIN0CdXps_lTLcCl3DfMsq-Mr1rUsURZ34A
_globalsign-domain-verification=l_BNpBAnk-rKZRyXJ9UkBfv9o6EEuuenkBrGpYNYo0
sonatype=OSSRH-45437
facebook-domain-verification=9lejgwdpdpmpxmg224rw9hhikrzafv
status-page-domain-verification=14p0vpzfmgky
google-site-verification=8a1XVuzDhK59toMTMRhHUdzQUi7hg_q1NqiIRluWESA
CAALookup not available with standard resolver
Resolved in 113 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://500px.com

https://500px.com

99 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://500px.com20099 msHTTP/1.1AmazonS3
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.500px.com/
200https://500px.com/

Preferred variant: non-www

HTTP → HTTPS

301http://500px.com/ https://500px.com/

Consistent

A+
Domain Intelligence
500px.com — via GoDaddy.com, LLC, 22 years old, hosted on AWS
PASS
500px.com — via GoDaddy.com, LLC, 22 years old, hosted on AWS
Info::
Domain registered until Jul 23, 2026 (3 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: AWS
Got: AS16509
Domain expiry

8 days

July 23, 2026

SSL certificate

137 days

Issued by Amazon

Domain age

22 years

Registered July 23, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

65.8.202.63

Registrar

GoDaddy.com, LLC

Unlocked 4 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 GoDaddy.com, LLC
Created July 23, 2004 (22 years ago)
Expires July 23, 2026 (3 months)
Last Updated July 24, 2025
Name Servers ns-1489.awsdns-58.org, ns-1537.awsdns-00.co.uk, ns-46.awsdns-05.com, ns-557.awsdns-05.net
DNSSEC Not enabled
Hosting
IP Address 65.8.202.63
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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

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

Connection waterfall

DNS Lookup 31 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 39 ms Content Transfer 0 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD56-P6)
Got: x-amz-cf-id: oKWLwu3EDq-E-zxqPUBU7fcvb3-pIgoTGLGa1l7V62hGCOibp-whPQ==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: oKWLwu3EDq-E-zxqPUBU7fcvb3-pIgoTGLGa1l7V62hGCOibp-whPQ==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback