Skip to content
https://pxhere.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Singapore, Singapore
403 Forbidden
Checks
9
6 PASS 3 REVIEW
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

86
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
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SIN)
Got: cf-ray: 9f0740f1dffbdaa5-SIN
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f0740f1dffbdaa5-SIN
A+
DNS Records
3 A records, 3 ms lookup
PASS
3 A records, 3 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.13.7, 172.67.70.214, 104.26.12.7
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::ac43:46d6, 2606:4700:20::681a:c07, 2606:4700:20::681a:d07
Info::
2 nameserver(s) configured
Got: stan.ns.cloudflare.com, vida.ns.cloudflare.com
Info::
2 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: 3 ms
Got: 3 ms
A104.26.13.7, 172.67.70.214, 104.26.12.7
AAAA2606:4700:20::ac43:46d6, 2606:4700:20::681a:c07, 2606:4700:20::681a:d07
CNAME
NSstan.ns.cloudflare.com, vida.ns.cloudflare.com
MX
5 mxn.mxhichina.com
10 mxw.mxhichina.com
TXT
google-site-verification=6OYLNAuR7kNa1RVNUGbmq-_RYfXj5ZCV6ByoSZ1vv9g
SPF v=spf1 include:spf.mxhichina.com -all
CAALookup not available with standard resolver
Resolved in 3 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
0 redirect(s), 20 ms total
PASS
0 redirect(s), 20 ms total

https://pxhere.com

20 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pxhere.com40320 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::ac43:46d6, 2606:4700:20::681a:c07, 2606:4700:20::681a:d07
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::ac43:46d6, 2606:4700:20::681a:c07, 2606:4700:20::681a:d07 Connection Reachable (1 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.pxhere.com/
200https://pxhere.com/

HTTP → HTTPS

301http://pxhere.com/ https://pxhere.com/

Consistent

A+
Domain Intelligence
pxhere.com — via Cloudflare, Inc., 9 years, 7 months old
PASS
pxhere.com — via Cloudflare, Inc., 9 years, 7 months old
Info::
Domain registered until Nov 4, 2027 (1 years, 6 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: Cloudflare, 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

475 days

November 4, 2027

SSL certificate

86 days

Issued by Google Trust Services

Domain age

9 years, 7 months

Registered November 4, 2016

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:c07

Registrar

Cloudflare, Inc.

Unlocked 2 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 Cloudflare, Inc.
Created November 4, 2016 (9 years, 7 months ago)
Expires November 4, 2027 (1 years, 6 months)
Last Updated March 16, 2024
Name Servers stan.ns.cloudflare.com, vida.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::681a:c07
Data source: rdap (0.8s)

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

Connection waterfall

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