Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CDNS RecordsAction1 A records, 738 ms lookupREVIEW
| A | 159.203.50.177 |
| AAAA | — |
| CNAME | geo.surge.world |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
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)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/1 IPs match cert SANREVIEW
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
CHTTP Probe TimingActionTotal 1947 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations86 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
CCDN & DeliveryActionAssets on Cloudflare (host cdn.shopify.com, 34 assets); document served directly from origin (DigitalOcean)REVIEW
Asset hosts on a CDN
- cdn.shopify.com — Cloudflare · assets: 34 · Cache Status: HIT
- images.unsplash.com — Fastly · assets: 12 · Cache Status: HIT, MISS
Other asset hosts
- fonts.googleapis.com — assets: 2 · below probe threshold
- www.googletagmanager.com — assets: 1 · below probe threshold
The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.
BOperational Status PageNo status page link detectedREVIEW
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
AMulti-Resolver DNS SpeedMean 38ms across 3 resolvers (spread 54ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://www.shreeinfotechsystems.com
249 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.shreeinfotechsystems.com | 200 | 249 ms | HTTP/1.1 | Surge |
A+Crawlabilityrobots.txt present, sitemap with 19 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
Sitemap: https://shreeinfotechsystems.com/sitemap.xml
A+Domain Intelligenceshreeinfotechsystems.com — via HOSTINGER operations, UAB, 3 days old, hosted on DigitalOceanPASS
360 days
September 15, 2027
86 days
Issued by Let's Encrypt
3 days
Registered September 15, 2026
Not enabled
Protects against DNS spoofing
DigitalOcean
ASN AS14061
138.197.235.123
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