Skip to content
https://abayaest.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 8 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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 162.159.143.27: lookup 162.159.143.27: 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.
Info::
PTR lookup failed for 172.66.3.23: lookup 172.66.3.23: 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.
Info::
PTR lookup failed for 2606:4700:7::30b: lookup 2606:4700:7::30b: 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.
Info::
PTR lookup failed for 2a06:98c1:58::30b: lookup 2a06:98c1:58::30b: 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
Multi-Resolver DNS Speed
Mean 57ms across 3 resolvers (spread 100ms)
REVIEW
Mean 57ms across 3 resolvers (spread 100ms)
Info::
Quad9: 22ms
Got: 22ms via 9.9.9.9:53
Info::
Google: 28ms
Got: 28ms via 8.8.8.8:53
Info::
Cloudflare: 122ms
Got: 122ms via 1.1.1.1:53
B
HTTP Probe Timing
Total 864 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
42 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
864 ms
Total Time Total request time from DNS lookup through full response.
865 ms

Connection waterfall

DNS Lookup 42 ms TCP Connect 17 ms TLS Handshake 24 ms Server Processing 781 ms Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
88 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • 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
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: 410, /health: 410, /healthz: 410, /ping: 410, /status: 410.
A+
DNS Records
2 A records, 40 ms lookup
PASS
2 A records, 40 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 162.159.143.27, 172.66.3.23
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:7::30b, 2a06:98c1:58::30b
Info::
2 nameserver(s) configured
Got: ns1.salla.cloud, ns2.salla.cloud
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 40 ms
Got: 40 ms
A162.159.143.27, 172.66.3.23
AAAA2606:4700:7::30b, 2a06:98c1:58::30b
CNAME—
NSns1.salla.cloud, ns2.salla.cloud
MX—
TXT
facebook-domain-verification=w3qz4ewpvt7u2gpjpw4stbcrvma2ee
google-site-verification=I8ZPaQJ8h7VC2BACUzKK2fqLgT03yCVMvc4Q5LkLHqA
CAALookup not available with standard resolver
Resolved in 40 ms

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)

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://abayaest.com

https://abayaest.com

145 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://abayaest.com200145 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:7::30b, 2a06:98c1:58::30b
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:7::30b, 2a06:98c1:58::30b Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 84 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 84 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
Sitemap: https://abayaest.com/sitemap.xml
User-agent: *
Allow: /
Disallow: /*<iframe
sitemap.xml 200 OK
Type Sitemap Index URLs 2 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::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.abayaest.com/
200https://abayaest.com/

Preferred variant: non-www

HTTP → HTTPS

301http://abayaest.com/ → https://abayaest.com/

Consistent

A+
Domain Intelligence
abayaest.com — via Name.com, Inc., 6 years, 7 months old
PASS
abayaest.com — via Name.com, Inc., 6 years, 7 months old
Info::
Domain registered until Mar 3, 2027 (5 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: Name.com, Inc.
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.
Domain expiry

156 days

March 3, 2027

SSL certificate

88 days

Issued by Google Trust Services

Domain age

6 years, 7 months

Registered March 3, 2020

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:7::30b

Registrar

Name.com, Inc.

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 Name.com, Inc.
Created March 3, 2020 (6 years, 7 months ago)
Expires March 3, 2027 (5 months)
Last Updated March 5, 2026
Name Servers ns1.salla.cloud, ns2.salla.cloud
DNSSEC Not enabled
Hosting
IP Address 2606:4700:7::30b
Data source: rdap (0.2s)

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
CDN & Delivery
Document on Cloudflare; assets also on Akamai
PASS
Document on Cloudflare; assets also on Akamai
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a409347408bc0161-CDG
Info::
CDN cache status: DYNAMIC
Info::
Assets on Cloudflare: cdn.salla.sa (assets: 80), cache HIT
Got: cf-ray: a40936d3fde19ec7-CDG
Info::
Assets on Cloudflare: cdn.assets.salla.network (assets: 41), cache HIT
Got: cf-ray: a40936d3fdf46f1d-CDG
Info::
Assets on Cloudflare: cdn.files.salla.network (assets: 18), cache DYNAMIC
Got: cf-ray: a40936d3f83dd886-CDG
Info::
Assets on Cloudflare: cdn.salla.network (assets: 17), cache HIT
Got: cf-ray: a40936d3fb29d0ab-CDG
Info::
Assets on Akamai: analytics.tiktok.com (assets: 3), cache TCP_MEM_HIT from a23-59-215-75.deploy.akamaitechnologies.com (AkamaiGHost/22.6.4-888a2d21768272d5e2d80e9762941e76) (-)
Got: x-akamai-request-id: 43b7215
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a409347408bc0161-CDG

Asset hosts on a CDN

  • cdn.salla.sa — Cloudflare · assets: 80 · Cache Status: HIT
  • cdn.assets.salla.network — Cloudflare · assets: 41 · Cache Status: HIT
  • cdn.files.salla.network — Cloudflare · assets: 18 · Cache Status: DYNAMIC
  • cdn.salla.network — Cloudflare · assets: 17 · Cache Status: HIT
  • analytics.tiktok.com — Akamai · assets: 3 · Cache Status: TCP_MEM_HIT from a23-59-215-75.deploy.akamaitechnologies.com (AkamaiGHost/22.6.4-888a2d21768272d5e2d80e9762941e76) (-)

Other asset hosts

  • www.googletagmanager.com — assets: 3 · Google
  • connect.facebook.net — assets: 2 · below probe threshold
  • cdn.portal.files.salla.network — assets: 1 · below probe threshold
  • cdn.sift.com — assets: 1 · below probe threshold
  • client-do9.pages.dev — assets: 1 · below probe threshold
  • sc-static.net — assets: 1 · below probe threshold
  • static.cloudflareinsights.com — assets: 1 · below probe threshold
  • static.hotjar.com — assets: 1 · below probe threshold
  • theme-features.github.io — assets: 1 · below probe threshold
  • tr.snapchat.com — assets: 1 · below probe threshold
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback