Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from New York, United Stated

200 OK

Checks

5 PASS 12 REVIEW

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

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).

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

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.

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 79.143.84.162 does not match any cert SAN: shahin.sbglobaldns.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.

Multi-Resolver DNS Speed

Action

Mean 164ms across 3 resolvers (spread 258ms)

REVIEW

Mean 164ms across 3 resolvers (spread 258ms)

Cloudflare: 2ms

Got: 2ms via 1.1.1.1:53

Quad9: 230ms

Got: 230ms via 9.9.9.9:53

Google: 260ms

Got: 260ms via 8.8.8.8:53

High latency spread between resolvers: 258ms (min 2ms / max 260ms)

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.

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

HTTP Probe Timing

Total 970 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

320 ms

TCP Connect

160 ms

TLS Handshake

169 ms

Time to First Byte

822 ms

Total Time

970 ms

Connection waterfall

DNS Lookup 320 ms TCP Connect 160 ms TLS Handshake 169 ms Server Processing 174 ms Content Transfer 148 ms

TLS Certificate Expiry & Recommendations

89 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

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

CDN & Delivery

Action

Assets on Cloudflare (host flagcdn.com, 60 assets); document served directly from origin

REVIEW

Assets on Cloudflare (host flagcdn.com, 60 assets); document served directly from origin

Document not behind existing CDN (Cloudflare serves the assets)

The page's subresources are delivered by Cloudflare (flagcdn.com, 60 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: a3ae607f7e539051-EWR

Assets on Cloudflare: flagcdn.com (assets: 60), cache HIT

Got: cf-ray: a3ae607f7e539051-EWR

Assets on a CDN, document is not: Cloudflare

Document origin not attributed

Asset hosts on a CDN

flagcdn.com — Cloudflare · assets: 60 · Cache Status: HIT

Other asset hosts

fonts.googleapis.com — assets: 2 · below probe threshold
cdn.tailwindcss.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.

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

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.

Operational Status Page

No status page link detected

REVIEW

No status page link detected

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.

Health Check Endpoint

No conventional health endpoint found

REVIEW

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.

DNS Records

1 A records, 446 ms lookup

PASS

1 A records, 446 ms lookup

Resolves to 1 IPv4 address(es)

Got: 79.143.84.162

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns1.chabokan.net, ns2.chabokan.net

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (446 ms)

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

Got: 446 ms

A	79.143.84.162
AAAA	—
CNAME	—
NS	ns1.chabokan.net, ns2.chabokan.net
MX	10 mail.chabookan.ir
TXT	SPF v=spf1 mx -all
CAA	Lookup not available with standard resolver

Resolved in 446 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

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

No CNAME record present

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://oraphia.ir/ordoc

https://oraphia.ir/ordoc

874 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://oraphia.ir/ordoc	200	874 ms	HTTP/1.1

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

301https://www.oraphia.ir/ordoc

200https://oraphia.ir/ordoc

Preferred variant: non-www

Trailing Slash

307https://oraphia.ir/ordoc/

200https://oraphia.ir/ordoc

HTTP → HTTPS

301http://oraphia.ir/ordoc → https://oraphia.ir/ordoc

Consistent

A+

Domain Intelligence

oraphia.ir — hosted on mobinidc - Mobin Arvand Infrastructure Company LTD, IR

PASS

oraphia.ir — hosted on mobinidc - Mobin Arvand Infrastructure Company LTD, IR

Hosting: mobinidc - Mobin Arvand Infrastructure Company LTD, IR

Got: AS215708

Domain expiry

Unknown

SSL certificate

89 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

mobinidc - Mobin Arvand Infrastructure Company LTD, IR

ASN AS215708

79.143.84.162

Registrar

Registrar unknown

Lock status unknown 2 NS records

Expiry timeline

Today

+1 year

SSL expiry Danger zone (≤30 days)

Registrar

Name Servers ns1.chabokan.net, ns2.chabokan.net

Hosting

IP Address 79.143.84.162

ASN AS215708 (mobinidc - Mobin Arvand Infrastructure Company LTD, IR)

Provider mobinidc - Mobin Arvand Infrastructure Company LTD, IR

Data source: whois (0.9s)

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