Skip to content
https://birsayt.az

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
8
PASS
8
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
8 PASS 8 REVIEW
C
DNSSEC
Action
Zone signed but parent has no DS record
REVIEW
Zone signed but parent has no DS record
Warning::
DNSSEC keys published but parent zone has no DS record
The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.
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.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.
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.
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
TLS Certificate Expiry & Recommendations
49 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

49
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, 47 assets); document served directly from origin
REVIEW
Assets on AWS CloudFront (host static.wixstatic.com, 47 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, 47 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: 47), cache Hit from cloudfront
Got: delegation d1cq301dpr7fww.cloudfront.net
Info::
Assets on Google Cloud CDN: static.parastorage.com (assets: 33), cache miss
Got: via: 1.1 varnish (Varnish/6.0), 1.1 google
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: 47 · Cache Status: Hit from cloudfront
  • static.parastorage.com — Google Cloud CDN · assets: 33 · Cache Status: miss

Other asset hosts

  • browser.sentry-cdn.com — assets: 2 · below probe threshold
  • connect.facebook.net — assets: 2 · below probe threshold
  • www.googletagmanager.com — assets: 2 · below probe threshold
  • cf06bdf3-5bab-4f20-b165-97fb723dac6a.wixappcloud.com — assets: 1 · below probe threshold
  • photouploadwix.inspon-cloud.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, 167 ms lookup
PASS
3 A records, 167 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 185.230.63.107, 185.230.63.186, 185.230.63.171
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns15.wixdns.net, ns14.wixdns.net
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 167 ms
Got: 167 ms
A185.230.63.107, 185.230.63.186, 185.230.63.171
AAAA—
CNAME—
NSns15.wixdns.net, ns14.wixdns.net
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 alt3.aspmx.l.google.com
50 alt4.aspmx.l.google.com
TXT
SPF v=spf1 include:_spf.google.com ~all
google-site-verification=yhnYCYL2Uqxd8qh7nThhp0aEBbXgXD8TPSrWiZNr1KM
CAALookup not available with standard resolver
Resolved in 167 ms
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 53ms across 3 resolvers (spread 65ms)
PASS
Mean 53ms across 3 resolvers (spread 65ms)
Info::
Google: 21ms
Got: 21ms via 8.8.8.8:53
Info::
Cloudflare: 52ms
Got: 52ms via 1.1.1.1:53
Info::
Quad9: 86ms
Got: 86ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 193 ms total
PASS
1 redirect(s), 193 ms total
Info::
Single redirect
Got: https://birsayt.az → https://www.birsayt.az/ (301)
Info::
WWW normalization redirect

https://birsayt.az

123 ms · HTTP/1.1

301

https://www.birsayt.az/

70 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://birsayt.az301123 msHTTP/1.1Pepyaka
2https://www.birsayt.az/40370 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 638 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 638 B Sitemaps referenced 4 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.birsayt.az/sitemap.xml
Sitemap: https://www.birsayt.az/en_en-sitemap.xml
Sitemap: https://www.birsayt.az/ru_ru-sitemap.xml
Sitemap: https://www.birsayt.az/tr_tr-sitemap.xml

# Auto generated, go to SEO Tools > Robots.txt Editor to change this
sitemap.xml 200 OK
Type Sitemap Index URLs 4 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

403https://www.birsayt.az/
200https://birsayt.az/

HTTP → HTTPS

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

Consistent

A+
HTTP Probe Timing
Total 244 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
104 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
37 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
44 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
244 ms
Total Time Total request time from DNS lookup through full response.
244 ms

Connection waterfall

DNS Lookup 104 ms TCP Connect 37 ms TLS Handshake 44 ms Server Processing 58 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
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