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 Santa Clara, United States

200 OK

Checks

3 PASS 12 REVIEW 2 FIX

Multi-Resolver DNS Speed

Action

Mean 344ms across 3 resolvers (spread 375ms)

FIX

Mean 344ms across 3 resolvers (spread 375ms)

Cloudflare: 202ms

Got: 202ms via 1.1.1.1:53

Google: 255ms

Got: 255ms via 8.8.8.8:53

Quad9: 577ms

Got: 577ms via 9.9.9.9:53

High latency spread between resolvers: 375ms (min 202ms / max 577ms)

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.

CDN & Delivery

Action

No CDN detected

FIX

No CDN detected

A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

DNS Records

1 A records, 640 ms lookup

REVIEW

1 A records, 640 ms lookup

Resolves to 1 IPv4 address(es)

Got: 188.120.227.67

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

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

DNS resolution is slow (640 ms)

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

Got: 640 ms

A	188.120.227.67
AAAA	—
CNAME	—
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

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

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 188.120.227.67 does not match any cert SAN: www.dev

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.

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.

URL Variants

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

REVIEW

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

HTTP version does not redirect to HTTPS

Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

https://www.dev.xn--80avc2av3a.xn--p1ai/

200https://dev.xn--80avc2av3a.xn--p1ai/

HTTP → HTTPS

403http://dev.xn--80avc2av3a.xn--p1ai/

HTTP version does not redirect to HTTPS

HTTP Probe Timing

Action

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

REVIEW

DNS Lookup

495 ms

TCP Connect

178 ms

TLS Handshake

182 ms

Time to First Byte

1.56 s

Total Time

1.92 s

Connection waterfall

DNS Lookup 495 ms TCP Connect 178 ms TLS Handshake 182 ms Server Processing 708 ms Content Transfer 357 ms

TLS Certificate Expiry & Recommendations

66 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

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

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: connection error, /healthz: connection error, /ping: 404, /status: 404.

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://dev.xn--80avc2av3a.xn--p1ai

https://dev.xn--80avc2av3a.xn--p1ai

1503 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://dev.xn--80avc2av3a.xn--p1ai	200	1503 ms	HTTP/1.1	nginx/1.22.1

A+

Domain Intelligence

xn--80avc2av3a.xn--p1ai — via RD-RF, 15 years, 8 months old, hosted on SELECTEL-MSK, RU

PASS

xn--80avc2av3a.xn--p1ai — via RD-RF, 15 years, 8 months old, hosted on SELECTEL-MSK, RU

Domain registered until Nov 11, 2026 (5 months remaining)

Registrar: RD-RF

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.

Hosting: SELECTEL-MSK, RU

Got: AS50340

Domain expiry

179 days

November 11, 2026

SSL certificate

66 days

Issued by Let's Encrypt

Domain age

15 years, 8 months

Registered November 11, 2010

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

SELECTEL-MSK, RU

ASN AS50340

77.223.120.194

Registrar

RD-RF

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar RD-RF

Created November 11, 2010 (15 years, 8 months ago)

Expires November 11, 2026 (5 months)

Name Servers dns1.yandex.net, dns2.yandex.net

Hosting

IP Address 77.223.120.194

ASN AS50340 (SELECTEL-MSK, RU)

Provider SELECTEL-MSK, RU

Data source: whois (0.7s)

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

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