Scanned sites / www.litcolaw.com / 2026-11-03-1807

www.litcolaw.com scan from 2026-11-03 18:07:15 UTC DR 39

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-11-03-1807

Scanned 2026-11-03 18:07:15 UTC, finished 2026-11-03 19:53:55 UTC. Found on page 3 of brave web search results

Site: https://www.litcolaw.com/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

87/ 100Good

On November 3, 2026 the Site Spider crawled 715 pages and 1000 assets of www.litcolaw.com, starting from https://www.litcolaw.com/. It scored 87 out of 100, a good result. 11 of 33 checks found something to fix, led by heavy assets (26), sitemap coverage (418), title tags (111); 9 checks passed. Most of the points went to heavy assets (−6), sitemap coverage (−3.7), title tags (−1.6). 13 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: High1 high, 5 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
715
Assets fetched
1000
Status
Completed
Checks with issues
11 of 33
CoverageJob finished, partial coverage

1,715 of 1,715 discovered URLs were fetched, 2,402 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 192 left unchecked.

  • Title tags111 issues
    111 of 418 pages have title issues. 262 noindex or canonicalized pages excluded.
    −1.6 points
  • Meta descriptions99 issues
    99 of 418 pages have meta description issues. 262 noindex or canonicalized pages excluded.
    −1.2 points
  • Headings1 issue
    1 of 418 pages have heading issues. 262 noindex or canonicalized pages excluded.
  • Broken links1 issue
    2 internal links point at 1 broken URL.
  • Links to other sites1 issue
    1 destination answered with an error, 146 could not be determined (timeouts, rate limits or refusals), 192 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.1 points
  • Redirects34 issues
    35 redirecting URLs, 0 of them chained.
    −0.2 points
  • Non-200 responses1 issue
    212 URLs did not return a 2xx response. 35 of them are pages, 1 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability11 issues
    11 of 680 indexable pages have indexability warnings.
    −0.2 points
  • Image alt textOK
    0 of 8328 image references have no alt attribute. 20 use an empty alt (decorative), which is fine.
  • Heavy assets26 issues
    26 assets larger than 500 KB among 1000 fetched assets.
    −6 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage418 issues
    1 sitemap listing 0 URLs: 418 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −3.7 points
  • Internal link counts441 noted
    Internal link counts for 500 pages; 441 worth a look.
  • Thin contentOK
    0 of 418 pages have fewer than 200 words. 262 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format8 noted
    8 of 715 page URLs are harder to read, share or cache than they need to be.
  • Canonicals262 noted
    262 of 680 pages have a canonical worth checking.
  • Robots directives680 noted
    680 pages carry a robots directive; 0 carry none.
  • Anchor text183 noted
    183 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure88 noted
    88 of 418 pages could use the title, heading and snippet space better. 262 noindex or canonicalized pages excluded.
  • Image weight and alt length46 noted
    46 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 680 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data212 noted
    680 of 418 indexable pages carry structured data: BreadcrumbList (680), ListItem (680), WebSite (680), Organization (680), WebPage (631). 212 pages with errors a rich result would fail on.
  • Near duplicates2 noted
    2 pages in 1 group read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 680 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positions27 noted
    27 of 417 linked pages are linked only from the template, never from another page's content.
  • Pagination9 noted
    35 pages in pagination sequences; 9 with problems.
  • Headers and cookies3 noted
    5 cookies set by the site, 3 missing a protective flag; 13 response headers recorded across 1715 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 680 pages; 255 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling78 noted
    78 words an English dictionary does not know, on 189 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2800 sites, median 80%, average 79%

www.litcolaw.com scores 87%, higher than 78% of the 2800 scanned sites. See the full ranking.

0661310%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 16 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 33 sites66%: 42 sites67%: 42 sites68%: 40 sites69%: 51 sites70%: 46 sites71%: 78 sites72%: 76 sites73%: 81 sites74%: 78 sites75%: 87 sites76%: 95 sites77%: 108 sites78%: 126 sites79%: 110 sites80%: 126 sites81%: 123 sites82%: 131 sites83%: 118 sites84%: 130 sites85%: 106 sites86%: 93 sites87%: 94 sites88%: 78 sites89%: 74 sites90%: 54 sites91%: 56 sites92%: 42 sites93%: 28 sites94%: 25 sites95%: 14 sites96%: 17 sites97%: 15 sites98%: 7 sites99%: 2 sites100%: 124 sites87% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

Your site has several critical SEO issues, including broken links and a lack of sitemap coverage. Prioritize resolving these to improve your site's visibility and performance.

  1. 1

    Fix Broken Links

    Why: Broken links hinder user experience and SEO rankings.

    How: Redirect or update the links to ensure they point to valid pages.

    Checks: broken-links

  2. 2

    Update Sitemap Coverage

    Why: Missing pages in your sitemap can lead to poor indexing.

    How: Include all crawled pages in your sitemap to enhance visibility.

    Checks: sitemap-coverage

  3. 3

    Reduce Redirects

    Why: Excessive redirects can harm site speed and user experience.

    How: Identify and directly link to the final URL instead of through redirects.

    Checks: redirects

  4. 4

    Optimize Title Tags

    Why: Title issues affect search visibility and click-through rates.

    How: Ensure all pages have unique and descriptive title tags of appropriate length.

    Checks: titles

  5. 5

    Improve Meta Descriptions

    Why: Meta description issues can impact search rankings and user engagement.

    How: Assign unique meta descriptions to pages lacking them and ensure they are within standard length.

    Checks: meta-descriptions

  6. 6

    Shrink Heavy Assets

    Why: Large assets can slow down page load times.

    How: Compress images and optimize file sizes to improve site speed.

    Checks: heavy-assets

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

The website has significant security issues, starting with unsecured HTTP pages and missing critical headers. Immediate action is needed to secure data, prevent interception, and mitigate vulnerabilities. Implement HTTPS site-wide, add security headers, and upgrade vulnerable libraries.

  • 1 high
  • 5 medium
  • 3 low
  • 1 info
  1. 1

    HTTP Pages Served Without HTTPSHigh

    Why it matters: 251 pages are served over plain HTTP, allowing potential interception and alteration of content.

    Fix: Implement a server-side redirect for all HTTP traffic to HTTPS.

    Evidence: HTTPS

  2. 2

    Missing Strict Transport Security HeaderMedium

    Why it matters: No pages send an HSTS header, increasing risk on HTTP connections.

    Fix: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to HTTP response headers.

    Evidence: HTTP Strict Transport Security

  3. 3

    Lack of Content Security PolicyMedium

    Why it matters: No CSP defined, allowing arbitrary script and style execution, increasing XSS risk.

    Fix: Add 'Content-Security-Policy: default-src 'self';' to HTTP response headers.

    Evidence: Content Security Policy

  4. 4

    No Clickjacking ProtectionMedium

    Why it matters: Missing X-Frame-Options header allows embedding of pages in frames, increasing clickjacking risk.

    Fix: Add 'X-Frame-Options: DENY' to HTTP response headers.

    Evidence: Clickjacking protection

  5. 5

    Cookies Lack Security FlagsMedium

    Why it matters: 89 cookies are missing HttpOnly, Secure, and SameSite flags, exposing them to attacks.

    Fix: Update cookies to include flags like 'HttpOnly; Secure; SameSite=Strict'.

    Evidence: Cookie flags

  6. 6

    Vulnerable jQuery Library DetectedMedium

    Why it matters: jQuery 3.1.3 has known vulnerabilities that could be exploited based on site usage.

    Fix: Upgrade jQuery to version 3.5.0 or later to mitigate these vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  7. 7

    Absence of MIME Sniffing ProtectionLow

    Why it matters: Without X-Content-Type-Options, browsers may misinterpret file types, leading to vulnerabilities.

    Fix: Add 'X-Content-Type-Options: nosniff' to HTTP response headers.

    Evidence: MIME sniffing protection

  8. 8

    Missing Referrer PolicyLow

    Why it matters: Absence of a referrer-policy can expose sensitive page URLs when users navigate away.

    Fix: Add 'Referrer-Policy: no-referrer' to HTTP response headers.

    Evidence: Referrer policy

  9. 9

    Software Version DisclosureLow

    Why it matters: Server responses reveal the framework without version, which can aid attackers.

    Fix: Consider removing 'X-Powered-By' or obfuscating the server details.

    Evidence: Software version disclosure

  10. 10

    Permissions Policy Not SetInfo

    Why it matters: Missing Permissions-Policy header may allow excessive access to features like camera and location.

    Fix: Add 'Permissions-Policy: geolocation=(none)' to HTTP response headers.

    Evidence: Permissions policy

What the checks found

  • FoundHTTPSHigh

    251 pages answered 200 over plain HTTP with no redirect to HTTPS, while 429 were served over HTTPS. Anyone on the network path can read or alter these pages.

    • http://www.litcolaw.com/about-us/client-testimonials/ → 200 over http
    • http://www.litcolaw.com/about-us/ → 200 over http
    • http://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → 200 over http
    • http://www.litcolaw.com/about-us/our-team/ → 200 over http
    • http://www.litcolaw.com/about-us/guiding-principles/ → 200 over http
    • http://www.litcolaw.com/about-us/lawyers-youll-love/ → 200 over http
    • http://www.litcolaw.com/litcocares/ → 200 over http
    • http://www.litcolaw.com/awards/ → 200 over http
    • http://www.litcolaw.com/news/a-quick-update-about-our-website/ → 200 over http
    • http://www.litcolaw.com/news/ → 200 over http
    • http://www.litcolaw.com/calgary/ → 200 over http
    • http://www.litcolaw.com/calgary/car-accident-lawyers/ → 200 over http
  • FoundHTTP Strict Transport SecurityMedium

    No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://www.litcolaw.com/ → no strict-transport-security
    • https://www.litcolaw.com/about-us/ → no strict-transport-security
    • https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no strict-transport-security
    • https://www.litcolaw.com/about-us/our-team/ → no strict-transport-security
    • https://www.litcolaw.com/about-us/client-testimonials/ → no strict-transport-security
    • https://www.litcolaw.com/about-us/guiding-principles/ → no strict-transport-security
    • https://www.litcolaw.com/about-us/lawyers-youll-love/ → no strict-transport-security
    • https://www.litcolaw.com/litcocares/ → no strict-transport-security
    • https://www.litcolaw.com/awards/ → no strict-transport-security
    • https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no strict-transport-security
    • https://www.litcolaw.com/news/ → no strict-transport-security
    • https://www.litcolaw.com/calgary/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 680 HTML pages send a Content-Security-Policy header or meta tag, so the browser has no restriction on where scripts, styles and frames may load from.

    • https://www.litcolaw.com/ → no content-security-policy
    • https://www.litcolaw.com/about-us/ → no content-security-policy
    • https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no content-security-policy
    • https://www.litcolaw.com/about-us/our-team/ → no content-security-policy
    • https://www.litcolaw.com/about-us/client-testimonials/ → no content-security-policy
    • https://www.litcolaw.com/about-us/guiding-principles/ → no content-security-policy
    • https://www.litcolaw.com/about-us/lawyers-youll-love/ → no content-security-policy
    • https://www.litcolaw.com/litcocares/ → no content-security-policy
    • https://www.litcolaw.com/awards/ → no content-security-policy
    • https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no content-security-policy
    • https://www.litcolaw.com/news/ → no content-security-policy
    • https://www.litcolaw.com/calgary/ → no content-security-policy
  • FoundClickjacking protectionMedium

    No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.

    • https://www.litcolaw.com/ → no x-frame-options
    • https://www.litcolaw.com/about-us/ → no x-frame-options
    • https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no x-frame-options
    • https://www.litcolaw.com/about-us/our-team/ → no x-frame-options
    • https://www.litcolaw.com/about-us/client-testimonials/ → no x-frame-options
    • https://www.litcolaw.com/about-us/guiding-principles/ → no x-frame-options
    • https://www.litcolaw.com/about-us/lawyers-youll-love/ → no x-frame-options
    • https://www.litcolaw.com/litcocares/ → no x-frame-options
    • https://www.litcolaw.com/awards/ → no x-frame-options
    • https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no x-frame-options
    • https://www.litcolaw.com/news/ → no x-frame-options
    • https://www.litcolaw.com/calgary/ → no x-frame-options
  • FoundMIME sniffing protectionLow

    No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://www.litcolaw.com/ → no x-content-type-options
    • https://www.litcolaw.com/about-us/ → no x-content-type-options
    • https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no x-content-type-options
    • https://www.litcolaw.com/about-us/our-team/ → no x-content-type-options
    • https://www.litcolaw.com/about-us/client-testimonials/ → no x-content-type-options
    • https://www.litcolaw.com/about-us/guiding-principles/ → no x-content-type-options
    • https://www.litcolaw.com/about-us/lawyers-youll-love/ → no x-content-type-options
    • https://www.litcolaw.com/litcocares/ → no x-content-type-options
    • https://www.litcolaw.com/awards/ → no x-content-type-options
    • https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no x-content-type-options
    • https://www.litcolaw.com/news/ → no x-content-type-options
    • https://www.litcolaw.com/calgary/ → no x-content-type-options
  • FoundReferrer policyLow

    No HTML page sends referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.

    • https://www.litcolaw.com/ → no referrer-policy
    • https://www.litcolaw.com/about-us/ → no referrer-policy
    • https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no referrer-policy
    • https://www.litcolaw.com/about-us/our-team/ → no referrer-policy
    • https://www.litcolaw.com/about-us/client-testimonials/ → no referrer-policy
    • https://www.litcolaw.com/about-us/guiding-principles/ → no referrer-policy
    • https://www.litcolaw.com/about-us/lawyers-youll-love/ → no referrer-policy
    • https://www.litcolaw.com/litcocares/ → no referrer-policy
    • https://www.litcolaw.com/awards/ → no referrer-policy
    • https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no referrer-policy
    • https://www.litcolaw.com/news/ → no referrer-policy
    • https://www.litcolaw.com/calgary/ → no referrer-policy
  • FoundPermissions policyInfo

    No HTML page sends permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.

    • https://www.litcolaw.com/ → no permissions-policy
    • https://www.litcolaw.com/about-us/ → no permissions-policy
    • https://www.litcolaw.com/about-us/our-team/lawyer-profiles/ → no permissions-policy
    • https://www.litcolaw.com/about-us/our-team/ → no permissions-policy
    • https://www.litcolaw.com/about-us/client-testimonials/ → no permissions-policy
    • https://www.litcolaw.com/about-us/guiding-principles/ → no permissions-policy
    • https://www.litcolaw.com/about-us/lawyers-youll-love/ → no permissions-policy
    • https://www.litcolaw.com/litcocares/ → no permissions-policy
    • https://www.litcolaw.com/awards/ → no permissions-policy
    • https://www.litcolaw.com/news/a-quick-update-about-our-website/ → no permissions-policy
    • https://www.litcolaw.com/news/ → no permissions-policy
    • https://www.litcolaw.com/calgary/ → no permissions-policy
  • FoundCookie flagsMedium

    89 of 91 cookies are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • SRsNAYkWrVjnLG (set by https://www.litcolaw.com/) lacks HttpOnly
    • wBpZTG (set by https://www.litcolaw.com/) lacks HttpOnly
    • nRhvtc-Yqo (set by https://www.litcolaw.com/) lacks HttpOnly
    • 03 Nov 2026 19:44:52 GMT (set by https://www.litcolaw.com/wp-content/uploads/elementor/css/post-975.css?ver=1793…) lacks Secure, HttpOnly, SameSite
    • 03 Nov 2026 19:44:53 GMT (set by https://www.litcolaw.com/wp-content/uploads/elementor/css/post-1789.css?ver=179…) lacks Secure, HttpOnly, SameSite
    • 03 Nov 2026 19:44:55 GMT (set by https://www.litcolaw.com/wp-content/uploads/elementor/css/post-1797.css?ver=179…) lacks Secure, HttpOnly, SameSite
    • 03 Nov 2026 19:44:56 GMT (set by https://www.litcolaw.com/wp-content/uploads/elementor/css/post-1188.css?ver=179…) lacks Secure, HttpOnly, SameSite
    • 03 Nov 2026 19:45:47 GMT (set by https://www.litcolaw.com/wp-content/uploads/elementor/css/post-1131.css?ver=179…) lacks Secure, HttpOnly, SameSite
    • 03 Nov 2026 19:45:51 GMT (set by https://www.litcolaw.com/wp-content/uploads/elementor/css/post-2090.css?ver=179…) lacks Secure, HttpOnly, SameSite
    • 03 Nov 2026 19:45:55 GMT (set by https://www.litcolaw.com/wp-content/uploads/elementor/css/post-883.css?ver=1793…) lacks Secure, HttpOnly, SameSite
    • 03 Nov 2026 19:45:56 GMT (set by https://www.litcolaw.com/wp-content/uploads/elementor/css/post-814.css?ver=1793…) lacks Secure, HttpOnly, SameSite
    • 03 Nov 2026 19:45:57 GMT (set by https://www.litcolaw.com/wp-content/uploads/elementor/css/post-812.css?ver=1793…) lacks Secure, HttpOnly, SameSite
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 3.1.3. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 3.1.3 in https://www.litcolaw.com/wp-content/plugins/gravityforms/js/placeholders.jquery…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: cloudflare (1715 responses)
    • x-powered-by: WP Engine (718 responses)
6 checks passed
  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    63 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • OKThird-party scripts

    The sampled pages load no scripts from other domains.

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

Sites scoring near www.litcolaw.com

Their neighbours in the SEO rank table, which orders every scanned site by health score.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

This report was produced by the DIY SEO Hub Site Spider crawling www.litcolaw.com from its pages as published, the way a search engine does. It shows summary figures only.

Own www.litcolaw.com?

  • Claim this site to manage the listing, hide it from the public lists, or keep it.
  • Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming www.litcolaw.com. Removal needs no account and no proof of purchase.