Skip to content
https://livejournal.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Sao Paulo, Brazil
302 Found
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
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.

B
Redirect Chain
1 redirect(s), 1927 ms total
REVIEW
1 redirect(s), 1927 ms total
Info::
Single redirect
Got: https://livejournal.com → https://www.livejournal.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://livejournal.com
Warning::
Redirect overhead: 1927 ms total
Got: 1927 ms

https://livejournal.com

965 ms · HTTP/1.1

302

https://www.livejournal.com/

962 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://livejournal.com302965 msHTTP/1.1nginx
2https://www.livejournal.com/200962 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

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

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.livejournal.com/
200https://livejournal.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://livejournal.com/ https://livejournal.com/

Consistent

B
TLS Certificate Expiry & Recommendations
345 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

345
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
A
DNS Records
2 A records, 241 ms lookup
PASS
2 A records, 241 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 81.19.74.0, 81.19.74.1
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns4.rambler.ru, ns3.rambler.ru, ns2.rambler.ru, ns5.rambler.ru
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (241 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 241 ms
A81.19.74.0, 81.19.74.1
AAAA
CNAME
NSns4.rambler.ru, ns3.rambler.ru, ns2.rambler.ru, ns5.rambler.ru
MX
10 mail.livejournal.com
TXT
_globalsign-domain-verification=6vanSW0uLnylNUqGRDWp2WCXal0ZKaJ2SWWayw2-hF
202202040808534a46fzt7ykgzgpiowim1m10aa98elk1rgd3ozc9i6t04xkx53j
google-site-verification=awx1FbEZ5jPCrDpdjUKWHaV-C3am6EvbLSNvpMbw158
_globalsign-domain-verification=rtXKyuEEqbGO7ulwJJXIjIJAtWolavpbYhQgkXrABb
google-site-verification=xfubMhw9dP3hzq4luAKmMTpLUD4vfkJj5zwRYycEWkw
google-site-verification=W-uhhNc0pBVo-6mqlVLFlcvn3PGgaFZ-34HrSbQsXyA
google-site-verification=glecFAHxpWw1tMrQDAXPVFGajV47ZKg-nrMdjIJU7WI
pinterest-site-verification=7cbedf8b1c1f0359c369e8c164518306
SPF v=spf1 mx ip4:81.19.74.0/24 -all
yandex-verification: 665ecaec263167db
google-site-verification=VKji3gXcdrpxxISo8SKC0CTIPjnpTLmXB3m5PzWMf4s
mailru-verification: feb6a343d2364125
google-site-verification=SxPKdBgk_M6gqbXW1158xM4JoLPczY4WS7UHLxCpCSoa
_globalsign-domain-verification=P7vynYgzeGlTSFNmmCBmgNeyu0unZOkydPRn1apam_
_globalsign-domain-verification=Sp9nROoH2HO_UR2sSnxhZlpQUhVFShSsK9rnKoogS_
CAALookup not available with standard resolver
Resolved in 241 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

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+
Crawlability
robots.txt present, sitemap with 339 URLs
PASS
robots.txt present, sitemap with 339 URLs
Info::
robots.txt is present
Got: 2643 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 339 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2643 B Sitemaps referenced 1 User-agents *, Yandex, spbot, AhrefsBot Blocking No — crawling allowed

User-agent: Yandex
Allow: /
Disallow: /allpics.bml
Disallow: /update.bml
Disallow: /identity
Disallow: /login.bml
Disallow: /manage
Disallow: /poll
Disallow: /profile
Disallow: /schools
Disallow: /todo
Disallow: /tools
Disallow: /update.bml
Disallow: /userinfo.bml
Disallow: /users
Allow: /ratings/$
Disallow: /ratings
Disallow: /syn
Disallow: /latest
Disallow: /ljtimes
Disallow: /talkread
Disallow: /inbox
Disallow: /misc
Disallow: /legal
Disallow: /checklistposts
Disallow: /away
Disallow: /rsearch
Disallow: /gsearch
Disallow: /register.bml
Disallow: /delcomment.bml
Disallow: /talkscreen.bml
Disallow: /give_tokens.bml
Clean-param: event&add&amp&area&askname&auth&authas&auto_forwhat
Clean-param: bookmark_off&cat&cc&change&cid&comm&country&ctc&date&del_filter&dest_name&dir
Clean-param: ELEMENT_ID&errmsg&expand&f116&f16&faqid&fb&filter&for&form&format&fp&fromuser&fs&g
Clean-param: gift&hash&id&iglocation&int_like&it&item&itemid&items&journal&keywords&lang&loc_ci&loc_cn
Clean-param: loc_st&m&metal&mode&moodtheme&name&nc&nodraft&nojs&nopics&opt_pagesize&opt_sort
Clean-param: ownerid&p&page&PAGEN_1&PAGEN_2&PAGEN_4&postID&ppid&prop_taglist&q&qid&ref&replyto&repost
Clean-param: repost_type&return&returnto&s&s_loc&s2id&sc&sessid&set_filter&show&sid&sign&sim&skip&sort&spam
Clean-param: st&start_search&state&stone&style&styleid&subject&subs_id&t
Clean-param: tab&tags&talkid&theme1&theme2&theme3&theme4&thread&title&to&type
Clean-param: u&uid&url&usejournal&uselang&user&userid&usescheme&view&xtor&y
Host: https://www.livejournal.com

User-Agent: spbot
Disallow: /

User-agent: AhrefsBot
Disallow: /

User-Agent: *
Allow: /
Disallow: /allpics.bml
Disallow: /update.bml
Disallow: /identity
Disallow: /login.bml
Disallow: /manage
Disallow: /poll
Disallow: /profile
Disallow: /schools
Disallow: /todo
Disallow: /tools
Disallow: /update.bml
Disallow: /userinfo.bml
Disallow: /users
Allow: /ratings/$
Disallow: /ratings
Disallow: /syn
Disallow: /latest
Disallow: /ljtimes
Disallow: /talkread
Disallow: /inbox
Disallow: /misc
Disallow: /legal
Disallow: /checklistposts
Disallow: /away
Disallow: /rsearch
Disallow: /gsearch
Disallow: /register.bml
Disallow: /delcomment.bml
Disallow: /talkscreen.bml
Disallow: /give_tokens.bml

Sitemap: https://www.livejournal.com/sitemap.xml

#
## Blocked journals aren't listed here because robots.txt files
## can't be above 50k or so, depending on the spider.
## 
## Instead, blocked journals have HTML inserted in them which
## should prevent behaved spiders from indexing it.
##
## Note that http://username.livejournal.com journals have an
## autogenerated robots.txt, since it can be small.
##
#
#

A+
Domain Intelligence
livejournal.com — via Regional Network Information Center, JSC dba RU-CENTER, 27 years, 4 months old, hosted on RAMBLER-TELECOM-AS, RU
PASS
livejournal.com — via Regional Network Information Center, JSC dba RU-CENTER, 27 years, 4 months old, hosted on RAMBLER-TELECOM-AS, RU
Info::
Domain registered until Apr 15, 2027 (1 years 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: Regional Network Information Center, JSC dba RU-CENTER
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: RAMBLER-TELECOM-AS, RU
Got: AS24638
Domain expiry

241 days

April 15, 2027

SSL certificate

345 days

Issued by GlobalSign nv-sa

Domain age

27 years, 4 months

Registered April 15, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

RAMBLER-TELECOM-AS, RU

ASN AS24638

81.19.74.0

Registrar

Regional Network Information Center, JSC dba RU-CENTER

Unlocked 4 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 Regional Network Information Center, JSC dba RU-CENTER
Created April 15, 1999 (27 years, 4 months ago)
Expires April 15, 2027 (1 years)
Last Updated March 15, 2026
Name Servers ns2.rambler.ru, ns3.rambler.ru, ns4.rambler.ru, ns5.rambler.ru
DNSSEC Not enabled
Hosting
IP Address 81.19.74.0
ASN AS24638 (RAMBLER-TELECOM-AS, RU)
Provider RAMBLER-TELECOM-AS, RU
Data source: rdap (0.6s)

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

Connection waterfall

DNS Lookup 3 ms TCP Connect 236 ms TLS Handshake 237 ms Server Processing 241 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback