Skip to content
https://multitek.in

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
17
8 PASS 9 REVIEW
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
0/3 IPs match cert SAN
REVIEW
0/3 IPs match cert SAN
Info::
PTR for 185.230.63.171 does not match any cert SAN: unalocated.63.wixsite.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 185.230.63.107 does not match any cert SAN: unalocated.63.wixsite.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 185.230.63.186 does not match any cert SAN: unalocated.63.wixsite.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.multitek.in/
200https://multitek.in/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://multitek.in/ → https://multitek.in/

Consistent

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

Certificate validity

77
days left
0d 30d 60d 90d+

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
C
CDN & Delivery
Action
Assets on AWS CloudFront (host static.wixstatic.com, 59 assets); document served directly from origin
REVIEW
Assets on AWS CloudFront (host static.wixstatic.com, 59 assets); document served directly from origin
Warning::
Document not behind existing CDN (AWS CloudFront serves the assets)
The page's subresources are delivered by AWS CloudFront (static.wixstatic.com, 59 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: delegation d1cq301dpr7fww.cloudfront.net
Info::
Assets on AWS CloudFront: static.wixstatic.com (assets: 59), cache Hit from cloudfront
Got: delegation d1cq301dpr7fww.cloudfront.net
Info::
Assets on AWS CloudFront: static.parastorage.com (assets: 30), cache Hit from cloudfront
Got: delegation d2v4ffmk60pnnm.cloudfront.net
Info::
Assets on AWS CloudFront: a.mailmunch.co (assets: 3), cache Hit from cloudfront
Got: delegation d3ar2nimg19ie1.cloudfront.net
Warning: Assets on a CDN, document is not: AWS CloudFront
Document origin not attributed

Asset hosts on a CDN

  • static.wixstatic.com — AWS CloudFront · assets: 59 · Cache Status: Hit from cloudfront
  • static.parastorage.com — AWS CloudFront · assets: 30 · Cache Status: Hit from cloudfront
  • a.mailmunch.co — AWS CloudFront · assets: 3 · Cache Status: Hit from cloudfront

Other asset hosts

  • www.googletagmanager.com — assets: 4 · Google
  • browser.sentry-cdn.com — assets: 2 · below probe threshold
  • googleads.g.doubleclick.net — assets: 2 · below probe threshold
  • cf06bdf3-5bab-4f20-b165-97fb723dac6a.wixappcloud.com — assets: 1 · below probe threshold
  • widget.privy.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.

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: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
3 A records, 211 ms lookup
PASS
3 A records, 211 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 185.230.63.171, 185.230.63.107, 185.230.63.186
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns0.wixdns.net, ns1.wixdns.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (211 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 211 ms
A185.230.63.171, 185.230.63.107, 185.230.63.186
AAAA—
CNAME—
NSns0.wixdns.net, ns1.wixdns.net
MX
10 aspmx.l.google.com
TXT
SPF v=spf1 include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 211 ms

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Multi-Resolver DNS Speed
Mean 56ms across 3 resolvers (spread 7ms)
PASS
Mean 56ms across 3 resolvers (spread 7ms)
Info::
Cloudflare: 53ms
Got: 53ms via 1.1.1.1:53
Info::
Quad9: 57ms
Got: 57ms via 9.9.9.9:53
Info::
Google: 60ms
Got: 60ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 649 ms total
PASS
1 redirect(s), 649 ms total
Info::
Single redirect
Got: https://multitek.in → https://www.multitek.in/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 649 ms total
Got: 649 ms

https://multitek.in

469 ms · HTTP/1.1

301

https://www.multitek.in/

180 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://multitek.in301469 msHTTP/1.1Pepyaka
2https://www.multitek.in/200180 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 489 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 489 B Sitemaps referenced 1 User-agents *, AdsBot-Google-Mobile, AdsBot-Google, PetalBot, dotbot, AhrefsBot Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: *?lightbox=

# Optimization for Google Ads Bot
User-agent: AdsBot-Google-Mobile
User-agent: AdsBot-Google
Disallow: /_partials*
Disallow: /pro-gallery-webapp/v1/galleries/*

# Block PetalBot
User-agent: PetalBot
Disallow: /

# Crawl delay for overly enthusiastic bots
User-agent: dotbot
Crawl-delay: 10
User-agent: AhrefsBot
Crawl-delay: 10

Sitemap: https://www.multitek.in/sitemap.xml

# Auto generated, go to SEO Tools > Robots.txt Editor to change this
sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
multitek.in — via Endurance International Group India Private Limited, 17 years, 2 months old, hosted on wix_com - Wix.com Ltd., IL
PASS
multitek.in — via Endurance International Group India Private Limited, 17 years, 2 months old, hosted on wix_com - Wix.com Ltd., IL
Info::
Domain registered until Sep 29, 2031 (5 years, 1 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: Endurance International Group India Private Limited
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.
Info::
Hosting: wix_com - Wix.com Ltd., IL
Got: AS58182
Domain expiry

1834 days

September 29, 2031

SSL certificate

77 days

Issued by Let's Encrypt

Domain age

17 years, 2 months

Registered September 29, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

wix_com - Wix.com Ltd., IL

ASN AS58182

185.230.63.171

Registrar

Endurance International Group India Private Limited

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 Endurance International Group India Private Limited
Created September 29, 2009 (17 years, 2 months ago)
Expires September 29, 2031 (5 years, 1 months)
Last Updated July 24, 2022
Name Servers ns1.wixdns.net, ns0.wixdns.net
DNSSEC Not enabled
Hosting
IP Address 185.230.63.171
ASN AS58182 (wix_com - Wix.com Ltd., IL)
Provider wix_com - Wix.com Ltd., IL
Data source: rdap (2.1s)

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

Connection waterfall

DNS Lookup 118 ms TCP Connect 116 ms TLS Handshake 122 ms Server Processing 161 ms Content Transfer 0 ms
A+
CDN Cache Observability
Cache state: fresh (Age=0)
PASS
Cache state: fresh (Age=0)
Info::
CDN cache state observable via 1 header(s)
Got: age=0
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback