Skip to content
https://pars-setia.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
9
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 193.36.85.27 does not match any cert SAN: rojivon.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
59 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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 Cloudflare (host flagcdn.com, 38 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host flagcdn.com, 38 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (flagcdn.com, 38 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: cf-ray: a4ddc90aca2b0053-CDG
Info::
Assets on Cloudflare: flagcdn.com (assets: 38), cache HIT
Got: cf-ray: a4ddc90aca2b0053-CDG
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • flagcdn.com — Cloudflare · assets: 38 · Cache Status: HIT

Other asset hosts

  • fonts.googleapis.com — assets: 2 · 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
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+
DNS Records
1 A records, 47 ms lookup
PASS
1 A records, 47 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 193.36.85.27
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns2.parspack.co, ns1.parspack.co, ns3.parspack.co, ns4.parspack.co
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 47 ms
Got: 47 ms
A193.36.85.27
AAAA—
CNAME—
NSns2.parspack.co, ns1.parspack.co, ns3.parspack.co, ns4.parspack.co
MX
10 mail.pars-setia.com
TXT
SPF v=spf1 mx a:mailgw-p.getway.biz a:imailgw-p.getway.biz -all
google-site-verification=gElk4h7DZLfvPSbDXaf6KHC9rCvJ2TdJTBasoJMGCTc
CAALookup not available with standard resolver
Resolved in 47 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

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 44ms across 3 resolvers (spread 9ms)
PASS
Mean 44ms across 3 resolvers (spread 9ms)
Info::
Quad9: 41ms
Got: 41ms via 9.9.9.9:53
Info::
Google: 43ms
Got: 43ms via 8.8.8.8:53
Info::
Cloudflare: 50ms
Got: 50ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://pars-setia.com

https://pars-setia.com

95 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pars-setia.com20095 msHTTP/1.1LiteSpeed
A+
Crawlability
robots.txt present, sitemap with 61 URLs
PASS
robots.txt present, sitemap with 61 URLs
Info::
robots.txt is present
Got: 395 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 61 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 395 B Sitemaps referenced 1 User-agents Google-Extended, ClaudeBot, PerplexityBot, *, GPTBot, OAI-SearchBot, ChatGPT-User Blocking No — crawling allowed
User-agent: *

Allow: /

Disallow: /admin/

Disallow: /cgi-bin/


# --- AI Crawlers (ChatGPT & Gemini) ---

User-agent: GPTBot

Allow: /


User-agent: OAI-SearchBot

Allow: /


User-agent: ChatGPT-User

Allow: /


User-agent: Google-Extended

Allow: /


User-agent: ClaudeBot

Allow: /


User-agent: PerplexityBot

Allow: /


# --- Sitemap ---

Sitemap: https://pars-setia.com/sitemap.php
sitemap.xml 200 OK
Type URL Set URLs 61 entries Valid XML Yes
Sample URLs:
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.pars-setia.com/
200https://pars-setia.com/

Preferred variant: non-www

HTTP → HTTPS

301http://pars-setia.com/ → https://pars-setia.com/

Consistent

A+
Domain Intelligence
pars-setia.com — via CSL Computer Service Langenbach GmbH d/b/a joker.com, 1 months old, hosted on BitCommand - BitCommand LLC, AM
PASS
pars-setia.com — via CSL Computer Service Langenbach GmbH d/b/a joker.com, 1 months old, hosted on BitCommand - BitCommand LLC, AM
Info::
Domain registered until Sep 20, 2027 (11 months remaining)
Info::
Domain is only 1 months old
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.
Got: Registered Sep 20, 2026
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: CSL Computer Service Langenbach GmbH d/b/a joker.com
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: BitCommand - BitCommand LLC, AM
Got: AS212552
Domain expiry

334 days

September 20, 2027

SSL certificate

59 days

Issued by Let's Encrypt

Domain age

1 months

Registered September 20, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

BitCommand - BitCommand LLC, AM

ASN AS212552

193.36.85.27

Registrar

CSL Computer Service Langenbach GmbH d/b/a joker.com

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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSL Computer Service Langenbach GmbH d/b/a joker.com
Created September 20, 2026 (1 months ago)
Expires September 20, 2027 (11 months)
Last Updated September 20, 2026
Name Servers ns1.parspack.co, ns2.parspack.co
DNSSEC Not enabled
Hosting
IP Address 193.36.85.27
ASN AS212552 (BitCommand - BitCommand LLC, AM)
Provider BitCommand - BitCommand LLC, AM
Data source: rdap (1.0s)

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.

Why this matters

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.

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

Connection waterfall

DNS Lookup 45 ms TCP Connect 30 ms TLS Handshake 33 ms Server Processing 31 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback