Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/2 IPs match cert SANREVIEW
BMulti-Resolver DNS SpeedMean 66ms across 3 resolvers (spread 119ms)REVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations87 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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
BOperational Status PageNo status page link detectedREVIEW
ADNS Records2 A records, 36 ms lookupPASS
| A | 64.29.17.1, 216.198.79.65 |
| AAAA | — |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Redirect ChainNo redirects — direct accessPASS
https://www.shreeinfotechsystems.com
74 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.shreeinfotechsystems.com | 200 | 74 ms | HTTP/1.1 | Vercel |
A+Crawlabilityrobots.txt present, sitemap with 4 URLsPASS
# ==============================================================================
# SHREE INFOTECH SYSTEMS — 2026 PRODUCTION ROBOTS DIRECTIVE
# Official Domain: https://shreeinfotechsystems.com
# ==============================================================================
User-agent: *
Allow: /
Allow: /catalog
Allow: /shop
Allow: /services
Allow: /brands
Allow: /reels
Allow: /about
Allow: /contact
Allow: /support
Allow: /wholesale-register
Allow: /wholesale-login
Allow: /privacy
Allow: /terms
Allow: /return
Allow: /warranty
Allow: /gst
Allow: /accessibility
Allow: /security
Allow: /cookies
Allow: /privacy-request
# Disallow Administrative Portals & Internal Endpoints
Disallow: /admin
Disallow: /admin-login
Disallow: /admin-dashboard
Disallow: /wholesale-dashboard
Disallow: /api/
# Search Engine Crawlers Specific Guidance
User-agent: Googlebot
Allow: /
User-agent: Bingbot
Allow: /
# Canonical XML Sitemap Index
Sitemap: https://shreeinfotechsystems.com/sitemap.xml
A+Domain Intelligenceshreeinfotechsystems.com — via HOSTINGER operations, UAB, 8 days old, hosted on AWSPASS
352 days
September 15, 2027
87 days
Issued by Let's Encrypt
8 days
Registered September 15, 2026
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
64.29.17.1
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
A+HTTP Probe TimingTotal 264 ms — DNS, TCP, TLS, TTFB, content transfer breakdownPASS
Connection waterfall
A+CDN & DeliveryDocument on Vercel; assets also on imgixPASS
Asset hosts on a CDN
- images.unsplash.com — imgix · assets: 12 · Cache Status: MISS, HIT
Other asset hosts
- www.googletagmanager.com — assets: 1 · below probe threshold