Skip to content
http://nexpixelhub.com

Infrastructure

· 16 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
2
REVIEW
7
PASS
7
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
16
7 PASS 7 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 262ms across 3 resolvers (spread 432ms)
FIX
Mean 262ms across 3 resolvers (spread 432ms)
Info::
Cloudflare: 3ms
Got: 3ms via 1.1.1.1:53
Info::
Google: 348ms
Got: 348ms via 8.8.8.8:53
Info::
Quad9: 435ms
Got: 435ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 432ms (min 3ms / max 435ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
4 PTR record(s) found (no cert data to match against)
REVIEW
4 PTR record(s) found (no cert data to match against)
Info::
PTR lookup failed for 2.57.91.170: lookup 2.57.91.170: no such host
Info::
PTR lookup failed for 84.32.84.140: lookup 84.32.84.140: no such host
Info::
PTR lookup failed for 2a02:4780:84:accf:28b7:f482:6841:ae0c: lookup 2a02:4780:84:accf:28b7:f482:6841:ae0c: no such host
Info::
PTR lookup failed for 2a02:4780:84:3d50:c377:f66a:8ee0:9366: lookup 2a02:4780:84:3d50:c377:f66a:8ee0:9366: no such host
B
Redirect Chain
1 redirect(s), 1108 ms total
REVIEW
1 redirect(s), 1108 ms total
Info::
Single redirect
Got: http://nexpixelhub.com → https://nexpixelhub.com/ (301)
Info::
HTTP to HTTPS redirect present
Warning::
Redirect overhead: 1108 ms total
Got: 1108 ms

http://nexpixelhub.com

545 ms · HTTP/1.1

301

https://nexpixelhub.com/

563 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1http://nexpixelhub.com301545 msHTTP/1.1hcdn
2https://nexpixelhub.com/200563 msHTTP/1.1hcdn

See the visual redirect chain in the HTTP Probe tab →

B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: connection error, /health: 404, /healthz: connection error, /ping: connection error, /status: connection error.
A+
DNS Records
2 A records, 123 ms lookup
PASS
2 A records, 123 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 2.57.91.170, 84.32.84.140
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:4780:84:accf:28b7:f482:6841:ae0c, 2a02:4780:84:3d50:c377:f66a:8ee0:9366
Info::
2 nameserver(s) configured
Got: orbit.dns-parking.com, horizon.dns-parking.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 123 ms
Got: 123 ms
A2.57.91.170, 84.32.84.140
AAAA2a02:4780:84:accf:28b7:f482:6841:ae0c, 2a02:4780:84:3d50:c377:f66a:8ee0:9366
CNAME—
NSorbit.dns-parking.com, horizon.dns-parking.com
MX
5 mx1.hostinger.com
10 mx2.hostinger.com
TXT
SPF v=spf1 include:_spf.mail.hostinger.com ~all
google-site-verification=JtN2Th9I8LC7G2NPrEEtV-NcNnCnMkrK1ZjL5gqmKGc
CAALookup not available with standard resolver
Resolved in 123 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2a02:4780:84:accf:28b7:f482:6841:ae0c, 2a02:4780:84:3d50:c377:f66a:8ee0:9366
Got: 2 ms connect
IPv6 Ready
AAAA Records 2a02:4780:84:accf:28b7:f482:6841:ae0c, 2a02:4780:84:3d50:c377:f66a:8ee0:9366 Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 321 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 321 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-content/uploads/wc-logs/
Disallow: /wp-content/uploads/woocommerce_transient_files/
Disallow: /wp-content/uploads/woocommerce_uploads/
Disallow: /*?add-to-cart=
Disallow: /*?*add-to-cart=
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://nexpixelhub.com/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 6 entries Valid XML Yes
Child Sitemaps:
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)

www / non-www

301http://www.nexpixelhub.com/
200http://nexpixelhub.com/

Preferred variant: non-www

A+
Domain Intelligence
nexpixelhub.com — via HOSTINGER operations, UAB, 3 months old
PASS
nexpixelhub.com — via HOSTINGER operations, UAB, 3 months old
Info::
Domain registered until Jul 15, 2027 (8 months remaining)
Info::
Domain is only 3 months old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Jul 15, 2026
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: HOSTINGER operations, UAB
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

264 days

July 15, 2027

SSL certificate

No certificate data

Domain age

3 months

Registered July 15, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:4780:84:85d6:3238:a103:b42:f128

Registrar

HOSTINGER operations, UAB

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar HOSTINGER operations, UAB
Created July 15, 2026 (3 months ago)
Expires July 15, 2027 (8 months)
Last Updated July 15, 2026
Name Servers horizon.dns-parking.com, orbit.dns-parking.com
DNSSEC Not enabled
Hosting
IP Address 2a02:4780:84:85d6:3238:a103:b42:f128
Data source: rdap (0.4s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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 382 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
114 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
0 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
382 ms
Total Time Total request time from DNS lookup through full response.
383 ms

Connection waterfall

DNS Lookup 114 ms TCP Connect 2 ms TLS Handshake 0 ms Server Processing 267 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