Infrastructure
· 16 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN (document or assets)FIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS4 PTR record(s) found (no cert data to match against)REVIEW
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
A+DNS Records2 A records, 119 ms lookupPASS
| A | 88.222.222.116, 84.32.84.252 |
| AAAA | 2a02:4780:84:4148:ef5:416f:dc76:fcf, 2a02:4780:84:275a:2ea2:958a:2d8d:9a3 |
| CNAME | — |
| NS | orbit.dns-parking.com, horizon.dns-parking.com |
| MX | 5 mx1.hostinger.com 10 mx2.hostinger.com |
| TXT | google-site-verification=JtN2Th9I8LC7G2NPrEEtV-NcNnCnMkrK1ZjL5gqmKGc SPF v=spf1 include:_spf.mail.hostinger.com ~all |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 21ms across 3 resolvers (spread 49ms)PASS
ARedirect Chain1 redirect(s), 306 ms totalPASS
http://nexpixelhub.com
63 ms · HTTP/1.1
https://nexpixelhub.com/
243 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | http://nexpixelhub.com | 301 | 63 ms | HTTP/1.1 | hcdn |
| 2 | https://nexpixelhub.com/ | 200 | 243 ms | HTTP/1.1 | hcdn |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (26 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 6 URLsPASS
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
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
A+Domain Intelligencenexpixelhub.com — via HOSTINGER operations, UAB, 3 months oldPASS
264 days
July 15, 2027
No certificate data
3 months
Registered July 15, 2026
Not enabled
Protects against DNS spoofing
Unknown
2a02:4780:84:275a:2ea2:958a:2d8d:9a3
HOSTINGER operations, UAB
Expiry timeline
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
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.
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.
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.
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