Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations262 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records1 A records, 131 ms lookupPASS
| A | 178.248.237.68 |
| AAAA | — |
| CNAME | — |
| NS | ns3.habradns.net, ns1.habradns.net, ns2.habradns.net |
| MX | 10 mxs.habramail.net |
| TXT | google-site-verification=XFULBM_wEq97-MNl8j--Pb07rVk_fy7e981d_6AEMjg yandex-verification: e86d27babf23ffa3 google-site-verification=-Lxx4RPV5xdNSkQo1PaDGlxZyQqohbnj08iYh1E53Kk SPF v=spf1 include:spf.habramail.net include:_spf.dashasender.ru ~all |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 594 ms totalPASS
https://habr.com
133 ms · HTTP/1.1
https://habr.com/ru/feed/
461 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://habr.com | 302 | 133 ms | HTTP/1.1 | QRATOR |
| 2 | https://habr.com/ru/feed/ | 200 | 461 ms | HTTP/1.1 | QRATOR |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
A+Crawlabilityrobots.txt present, sitemap with 22 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: Yandex
Disallow: /search/
Disallow: /ru/search/
Disallow: /en/search/
Disallow: /ru/companies/*/fans/
Disallow: /en/companies/*/fans/
Disallow: /ru/companies/*/workers/
Disallow: /en/companies/*/workers/
Disallow: /ru/users/*/followers/
Disallow: /en/users/*/followers/
Disallow: /ru/users/*/following/
Disallow: /en/users/*/following/
Clean-param: utm_source&utm_medium&utm_term&utm_campaign /
User-agent: Googlebot
Disallow: /search/
Disallow: /ru/search/
Disallow: /en/search/
Disallow: /*?*utm_source=
Disallow: /*?*utm_medium=
Disallow: /*?*utm_term=
Disallow: /*?*utm_campaign=
Disallow: /ru/companies/*/fans/
Disallow: /en/companies/*/fans/
Disallow: /ru/companies/*/workers/
Disallow: /en/companies/*/workers/
Disallow: /ru/users/*/followers/
Disallow: /en/users/*/followers/
Disallow: /ru/users/*/following/
Disallow: /en/users/*/following/
User-agent: Slurp
Crawl-delay: 8
Disallow: /search/
Disallow: /ru/search/
Disallow: /en/search/
Disallow: /*?*utm_
Disallow: /ru/companies/*/fans/
Disallow: /en/companies/*/fans/
Disallow: /ru/companies/*/workers/
Disallow: /en/companies/*/workers/
Disallow: /ru/users/*/followers/
Disallow: /en/users/*/followers/
Disallow: /ru/users/*/following/
Disallow: /en/users/*/following/
User-agent: *
Crawl-delay: 10
Disallow: /search/
Disallow: /ru/search/
Disallow: /en/search/
Disallow: /*?*utm_
Disallow: /ru/companies/*/fans/
Disallow: /en/companies/*/fans/
Disallow: /ru/companies/*/workers/
Disallow: /en/companies/*/workers/
Disallow: /ru/users/*/followers/
Disallow: /en/users/*/followers/
Disallow: /ru/users/*/following/
Disallow: /en/users/*/following/
- https://habr.com/sitemap_hubs.xml
- https://habr.com/sitemap_companies.xml
- https://habr.com/sitemap_articles1.xml
- https://habr.com/sitemap_articles2.xml
- https://habr.com/sitemap_articles3.xml
- https://habr.com/sitemap_articles4.xml
- https://habr.com/sitemap_articles5.xml
- https://habr.com/sitemap_articles6.xml
- https://habr.com/sitemap_articles7.xml
- https://habr.com/sitemap_articles8.xml
- https://habr.com/sitemap_articles9.xml
- https://habr.com/sitemap_articles10.xml
- https://habr.com/sitemap_articles11.xml
- https://habr.com/sitemap_articles12.xml
- https://habr.com/sitemap_articles13.xml
- https://habr.com/sitemap_articles14.xml
- https://habr.com/sitemap_articles15.xml
- https://habr.com/sitemap_news1.xml
- https://habr.com/sitemap_news2.xml
- https://habr.com/sitemap_news3.xml
- https://habr.com/sitemap_posts1.xml
- https://habr.com/sitemap_specials1.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencehabr.com — via Internet Domain Service BS Corp, 23 years, 5 months old, hosted on HLL-AS, RUPASS
604 days
March 11, 2028
262 days
Issued by Sectigo Limited
23 years, 5 months
Registered March 11, 2003
Enabled
Protects against DNS spoofing
HLL-AS, RU
ASN AS51115
178.248.237.68
Internet Domain Service BS Corp
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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