Skip to content
https://mikrorayonservis.az

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
10
PASS
4
INFO
1
Probed from Madrid, Spain
200 OK
Checks
17
4 PASS 10 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 293ms across 3 resolvers (spread 305ms)
FIX
Mean 293ms across 3 resolvers (spread 305ms)
Info::
Google: 124ms
Got: 124ms via 8.8.8.8:53
Info::
Cloudflare: 326ms
Got: 326ms via 1.1.1.1:53
Info::
Quad9: 429ms
Got: 429ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 305ms (min 124ms / max 429ms)
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
DNS Records
1 A records, 295 ms lookup
REVIEW
1 A records, 295 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 162.244.92.2
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2602:faa9:1007:955:209b:48c2:8ff2:ee73
Info::
2 nameserver(s) configured
Got: ns1.azhosting.space, ns2.azhosting.space
Info::
4 mail exchanger(s) configured
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (295 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 295 ms
A162.244.92.2
AAAA2602:faa9:1007:955:209b:48c2:8ff2:ee73
CNAME—
NSns1.azhosting.space, ns2.azhosting.space
MX
10 mx1.cpanelplatform.com
10 mx2.cpanelplatform.com
20 mx3.cpanelplatform.com
30 mx4.cpanelplatform.com
TXT
google-site-verification=Ra6D4KJz_rt7bmkED42jldQ3MlGFddOmCiTxs9BycA0
CAALookup not available with standard resolver
Resolved in 295 ms

Multiple A records provide failover if one server goes down.

Why this matters

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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

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.

Why this matters

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

Source: DNS performance benchmarks

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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 162.244.92.2 does not match any cert SAN: lv-shared03.cpanelplatform.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 lookup failed for 2602:faa9:1007:955:209b:48c2:8ff2:ee73: lookup 2602:faa9:1007:955:209b:48c2:8ff2:ee73: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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.mikrorayonservis.az/
200https://mikrorayonservis.az/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://mikrorayonservis.az/ → https://mikrorayonservis.az/

Consistent

B
HTTP Probe Timing
Total 918 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
426 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
162 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
164 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
918 ms
Total Time Total request time from DNS lookup through full response.
919 ms

Connection waterfall

DNS Lookup 426 ms TCP Connect 162 ms TLS Handshake 164 ms Server Processing 165 ms Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
75 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
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: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://mikrorayonservis.az

https://mikrorayonservis.az

491 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mikrorayonservis.az200491 msHTTP/1.1LiteSpeed
A+
IPv6 Readiness
IPv6 reachable (163 ms)
PASS
IPv6 reachable (163 ms)
Info::
IPv6 is configured and reachable at 2602:faa9:1007:955:209b:48c2:8ff2:ee73
Got: 163 ms connect
IPv6 Ready
AAAA Records 2602:faa9:1007:955:209b:48c2:8ff2:ee73 Connection Reachable (163 ms)
A+
Crawlability
robots.txt present, sitemap with 13 URLs
PASS
robots.txt present, sitemap with 13 URLs
Info::
robots.txt is present
Got: 544 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 13 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 544 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# MikrorayonServis – robots.txt
# https://mikrorayonservis.az

User-agent: *
Allow: /
Allow: /*.css$
Allow: /*.js$
Allow: /images/

Disallow: /admin/
Disallow: /private/
Disallow: /node_modules/
Disallow: /src/
Disallow: /scripts/
Disallow: /tmp/
Disallow: /_inc/
Disallow: /_page_
Disallow: /package.json
Disallow: /package-lock.json
Disallow: /eslint.config.js
Disallow: /.htmlvalidate.json
Disallow: /TODO.md
Disallow: /pages-meta.json
Disallow: /_tmp/
Disallow: /*.tgz$
Disallow: /*.ps1$

Sitemap: https://mikrorayonservis.az/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 13 entries Valid XML Yes
Sample URLs:
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback