🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 159 (from laksa103)

2. Crawled Status Check

Query:

Response:

{"found_url":"https:\/\/git-lfs.com\/","crawl_time":1776552286,"first_indexed_time":1578248064,"http_code":200,"src_unparsed":"com,git-lfs!\/ s443","src_root_hash":"12278960552995301759","history_drop_reason":null,"meta_title":"Git Large File Storage | Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.","meta_descriptions":["Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise."],"attrs_boilerpipe_text":"Getting Started\nDownload and install the Git command line extension. Once downloaded and installed, set up Git LFS for your user account by running:\ngit lfs install\nYou only need to run this once per user account.\nIn each Git repository where you want to use Git LFS, select the file types you'd like Git LFS to manage (or directly edit your .gitattributes). You can configure additional file extensions at anytime.\ngit lfs track \"*.psd\"\nNow make sure .gitattributes is tracked:\ngit add .gitattributes\nNote that defining the file types Git LFS should track will not, by itself, convert any pre-existing files to Git LFS, such as files on other branches or in your prior commit history. To do that, use the\ngit lfs migrate(1)\ncommand, which has a range of options designed to suit various potential use cases.\nThere is no step three. Just commit and push as you normally would; for instance, if your current branch is named\nmain\n:\ngit add file.psd\ngit commit -m \"Add design file\"\ngit push origin main\nCheck out our\nwiki\n,\ndiscussion forum\n, and\ndocumentation\nfor help with any questions you might have!\nGit LFS is an open source project\nTo start a discussion, file an issue, or contribute to the project, head over\nto the repository\nor read our\nguide to contributing\n.\nIf you're interested in integrating Git LFS into another tool or product, you might want to read the\nAPI specification\nor check out our\nreference server implementation\n.\nFeatures\nLarge file versioning\nVersion large files—even those as large as a couple GB in size—with Git.\nMore repository space\nHost more in your Git repositories. External file storage makes it easy to keep your repository at a manageable size.\nFaster cloning and fetching\nDownload less data. This means faster cloning and fetching from repositories that deal with large files.\nSame Git workflow\nWork like you always do on Git—no need for additional commands, secondary storage systems, or toolsets.\nSame access controls and permissions\nKeep the same access controls and permissions for large files as the rest of your Git repository when working with a remote host like GitHub.","attrs_markdown":"[Docs](https:\/\/github.com\/git-lfs\/git-lfs\/tree\/main\/docs?utm_source=gitlfs_site&utm_medium=docs_link&utm_campaign=gitlfs) [Discussions](https:\/\/github.com\/git-lfs\/git-lfs\/discussions?utm_source=gitlfs_site&utm_medium=discussions_link&utm_campaign=gitlfs) [Wiki](https:\/\/github.com\/git-lfs\/git-lfs\/wiki?utm_source=gitlfs_site&utm_medium=wiki_link&utm_campaign=gitlfs) [Installation](https:\/\/github.com\/git-lfs\/git-lfs?utm_source=gitlfs_site&utm_medium=installation_link&utm_campaign=gitlfs#installing) [Releases](https:\/\/github.com\/git-lfs\/git-lfs\/releases?utm_source=gitlfs_site&utm_medium=releases_link&utm_campaign=gitlfs) [Source](https:\/\/github.com\/git-lfs\/git-lfs?utm_source=gitlfs_site&utm_medium=source_link&utm_campaign=gitlfs)\n\n# An open source Git extension for versioning large files\nGit Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.\n\n[Download v3.7.1 (Windows)](https:\/\/github.com\/git-lfs\/git-lfs\/releases\/download\/v3.7.1\/git-lfs-windows-v3.7.1.exe)\n\n[Download v3.7.1 (Mac - Intel Silicon)](https:\/\/github.com\/git-lfs\/git-lfs\/releases\/download\/v3.7.1\/git-lfs-darwin-amd64-v3.7.1.zip)\n\n[Download v3.7.1 (Mac - Apple Silicon)](https:\/\/github.com\/git-lfs\/git-lfs\/releases\/download\/v3.7.1\/git-lfs-darwin-arm64-v3.7.1.zip)\n\n[Homebrew](http:\/\/brew.sh\/): `brew install git-lfs`  \n [MacPorts](https:\/\/www.macports.org\/): `port install git-lfs`\n\n[Install v3.7.1 via PackageCloud (Linux)](https:\/\/packagecloud.io\/github\/git-lfs\/install)\n\n[Download v3.7.1 (Linux - x86-64)](https:\/\/github.com\/git-lfs\/git-lfs\/releases\/download\/v3.7.1\/git-lfs-linux-amd64-v3.7.1.tar.gz)\n\n## How it works:\n![a diagram showing how Git LFS works](https:\/\/git-lfs.com\/images\/graphic.gif)\n\n[Git LFS security update: All users should update to 3.7.1.](https:\/\/github.com\/git-lfs\/git-lfs\/security\/advisories\/GHSA-6pvw-g552-53c5)\n\n## Getting Started\n1. Download and install the Git command line extension. Once downloaded and installed, set up Git LFS for your user account by running:\n   ```\n   git lfs install\n   ```\n   You only need to run this once per user account.\n2. In each Git repository where you want to use Git LFS, select the file types you'd like Git LFS to manage (or directly edit your .gitattributes). You can configure additional file extensions at anytime.\n   ```\n   git lfs track \"*.psd\"\n   ```\n   Now make sure .gitattributes is tracked:\n   ```\n   git add .gitattributes\n   ```\n   Note that defining the file types Git LFS should track will not, by itself, convert any pre-existing files to Git LFS, such as files on other branches or in your prior commit history. To do that, use the [git lfs migrate(1)](https:\/\/github.com\/git-lfs\/git-lfs\/blob\/main\/docs\/man\/git-lfs-migrate.adoc?utm_source=gitlfs_site&utm_medium=doc_man_migrate_link&utm_campaign=gitlfs) command, which has a range of options designed to suit various potential use cases.\n3. There is no step three. Just commit and push as you normally would; for instance, if your current branch is named `main`:\n   ```\n   git add file.psd\ngit commit -m \"Add design file\"\ngit push origin main\n   ```\n   Check out our [wiki](https:\/\/github.com\/git-lfs\/git-lfs\/wiki?utm_source=gitlfs_site&utm_medium=wiki_link&utm_campaign=gitlfs), [discussion forum](https:\/\/github.com\/git-lfs\/git-lfs\/discussions?utm_source=gitlfs_site&utm_medium=discussions_link&utm_campaign=gitlfs), and [documentation](https:\/\/github.com\/git-lfs\/git-lfs\/tree\/main\/docs?utm_source=gitlfs_site&utm_medium=docs_link&utm_campaign=gitlfs) for help with any questions you might have\\!\n## Git LFS is an open source project\nTo start a discussion, file an issue, or contribute to the project, head over [to the repository](https:\/\/github.com\/git-lfs\/git-lfs?utm_source=gitlfs_site&utm_medium=repo_link&utm_campaign=gitlfs) or read our [guide to contributing](https:\/\/github.com\/git-lfs\/git-lfs\/blob\/main\/CONTRIBUTING.md?utm_source=gitlfs_site&utm_medium=contributing_link&utm_campaign=gitlfs).\n\nIf you're interested in integrating Git LFS into another tool or product, you might want to read the [API specification](https:\/\/github.com\/git-lfs\/git-lfs\/blob\/main\/docs\/api\/README.md?utm_source=gitlfs_site&utm_medium=api_spec_link&utm_campaign=gitlfs) or check out our [reference server implementation](https:\/\/github.com\/git-lfs\/lfs-test-server?utm_source=gitlfs_site&utm_medium=reference_servedr&utm_campaign=gitlfs).\n\n## Features\n- ### Large file versioning\n  Version large files—even those as large as a couple GB in size—with Git.\n- ### More repository space\n  Host more in your Git repositories. External file storage makes it easy to keep your repository at a manageable size.\n- ### Faster cloning and fetching\n  Download less data. This means faster cloning and fetching from repositories that deal with large files.\n- ### Same Git workflow\n  Work like you always do on Git—no need for additional commands, secondary storage systems, or toolsets.\n- ### Same access controls and permissions\n  Keep the same access controls and permissions for large files as the rest of your Git repository when working with a remote host like GitHub.\n\n[with by .](https:\/\/github.com\/?utm_source=gitlfs_site&utm_medium=footer&utm_campaign=gitlfs)\n\nGit is a trademark of the [Software Freedom Conservancy](http:\/\/sfconservancy.org\/).","attrs_readable_markdown":"## Getting Started\n1. Download and install the Git command line extension. Once downloaded and installed, set up Git LFS for your user account by running:\n   ```\n   git lfs install\n   ```\n   You only need to run this once per user account.\n2. In each Git repository where you want to use Git LFS, select the file types you'd like Git LFS to manage (or directly edit your .gitattributes). You can configure additional file extensions at anytime.\n   ```\n   git lfs track \"*.psd\"\n   ```\n   Now make sure .gitattributes is tracked:\n   ```\n   git add .gitattributes\n   ```\n   Note that defining the file types Git LFS should track will not, by itself, convert any pre-existing files to Git LFS, such as files on other branches or in your prior commit history. To do that, use the [git lfs migrate(1)](https:\/\/github.com\/git-lfs\/git-lfs\/blob\/main\/docs\/man\/git-lfs-migrate.adoc?utm_source=gitlfs_site&utm_medium=doc_man_migrate_link&utm_campaign=gitlfs) command, which has a range of options designed to suit various potential use cases.\n3. There is no step three. Just commit and push as you normally would; for instance, if your current branch is named `main`:\n   ```\n   git add file.psd\ngit commit -m \"Add design file\"\ngit push origin main\n   ```\n   Check out our [wiki](https:\/\/github.com\/git-lfs\/git-lfs\/wiki?utm_source=gitlfs_site&utm_medium=wiki_link&utm_campaign=gitlfs), [discussion forum](https:\/\/github.com\/git-lfs\/git-lfs\/discussions?utm_source=gitlfs_site&utm_medium=discussions_link&utm_campaign=gitlfs), and [documentation](https:\/\/github.com\/git-lfs\/git-lfs\/tree\/main\/docs?utm_source=gitlfs_site&utm_medium=docs_link&utm_campaign=gitlfs) for help with any questions you might have\\!\n## Git LFS is an open source project\nTo start a discussion, file an issue, or contribute to the project, head over [to the repository](https:\/\/github.com\/git-lfs\/git-lfs?utm_source=gitlfs_site&utm_medium=repo_link&utm_campaign=gitlfs) or read our [guide to contributing](https:\/\/github.com\/git-lfs\/git-lfs\/blob\/main\/CONTRIBUTING.md?utm_source=gitlfs_site&utm_medium=contributing_link&utm_campaign=gitlfs).\n\nIf you're interested in integrating Git LFS into another tool or product, you might want to read the [API specification](https:\/\/github.com\/git-lfs\/git-lfs\/blob\/main\/docs\/api\/README.md?utm_source=gitlfs_site&utm_medium=api_spec_link&utm_campaign=gitlfs) or check out our [reference server implementation](https:\/\/github.com\/git-lfs\/lfs-test-server?utm_source=gitlfs_site&utm_medium=reference_servedr&utm_campaign=gitlfs).\n\n## Features\n- ### Large file versioning\n  Version large files—even those as large as a couple GB in size—with Git.\n- ### More repository space\n  Host more in your Git repositories. External file storage makes it easy to keep your repository at a manageable size.\n- ### Faster cloning and fetching\n  Download less data. This means faster cloning and fetching from repositories that deal with large files.\n- ### Same Git workflow\n  Work like you always do on Git—no need for additional commands, secondary storage systems, or toolsets.\n- ### Same access controls and permissions\n  Keep the same access controls and permissions for large files as the rest of your Git repository when working with a remote host like GitHub.","meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

1 hour ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	0 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://git-lfs.com/
Last Crawled	2026-04-18 22:44:46 (1 hour ago)
First Indexed	2020-01-05 18:14:24 (6 years ago)
HTTP Status Code	200
Meta Title	Git Large File Storage \| Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.
Meta Description	Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.
Meta Canonical	null
Boilerpipe Text	Getting Started Download and install the Git command line extension. Once downloaded and installed, set up Git LFS for your user account by running: git lfs install You only need to run this once per user account. In each Git repository where you want to use Git LFS, select the file types you'd like Git LFS to manage (or directly edit your .gitattributes). You can configure additional file extensions at anytime. git lfs track "*.psd" Now make sure .gitattributes is tracked: git add .gitattributes Note that defining the file types Git LFS should track will not, by itself, convert any pre-existing files to Git LFS, such as files on other branches or in your prior commit history. To do that, use the git lfs migrate(1) command, which has a range of options designed to suit various potential use cases. There is no step three. Just commit and push as you normally would; for instance, if your current branch is named main : git add file.psd git commit -m "Add design file" git push origin main Check out our wiki , discussion forum , and documentation for help with any questions you might have! Git LFS is an open source project To start a discussion, file an issue, or contribute to the project, head over to the repository or read our guide to contributing . If you're interested in integrating Git LFS into another tool or product, you might want to read the API specification or check out our reference server implementation . Features Large file versioning Version large files—even those as large as a couple GB in size—with Git. More repository space Host more in your Git repositories. External file storage makes it easy to keep your repository at a manageable size. Faster cloning and fetching Download less data. This means faster cloning and fetching from repositories that deal with large files. Same Git workflow Work like you always do on Git—no need for additional commands, secondary storage systems, or toolsets. Same access controls and permissions Keep the same access controls and permissions for large files as the rest of your Git repository when working with a remote host like GitHub.
Markdown	[Docs](https://github.com/git-lfs/git-lfs/tree/main/docs?utm_source=gitlfs_site&utm_medium=docs_link&utm_campaign=gitlfs) [Discussions](https://github.com/git-lfs/git-lfs/discussions?utm_source=gitlfs_site&utm_medium=discussions_link&utm_campaign=gitlfs) [Wiki](https://github.com/git-lfs/git-lfs/wiki?utm_source=gitlfs_site&utm_medium=wiki_link&utm_campaign=gitlfs) [Installation](https://github.com/git-lfs/git-lfs?utm_source=gitlfs_site&utm_medium=installation_link&utm_campaign=gitlfs#installing) [Releases](https://github.com/git-lfs/git-lfs/releases?utm_source=gitlfs_site&utm_medium=releases_link&utm_campaign=gitlfs) [Source](https://github.com/git-lfs/git-lfs?utm_source=gitlfs_site&utm_medium=source_link&utm_campaign=gitlfs) # An open source Git extension for versioning large files Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise. [Download v3.7.1 (Windows)](https://github.com/git-lfs/git-lfs/releases/download/v3.7.1/git-lfs-windows-v3.7.1.exe) [Download v3.7.1 (Mac - Intel Silicon)](https://github.com/git-lfs/git-lfs/releases/download/v3.7.1/git-lfs-darwin-amd64-v3.7.1.zip) [Download v3.7.1 (Mac - Apple Silicon)](https://github.com/git-lfs/git-lfs/releases/download/v3.7.1/git-lfs-darwin-arm64-v3.7.1.zip) [Homebrew](http://brew.sh/): `brew install git-lfs` [MacPorts](https://www.macports.org/): `port install git-lfs` [Install v3.7.1 via PackageCloud (Linux)](https://packagecloud.io/github/git-lfs/install) [Download v3.7.1 (Linux - x86-64)](https://github.com/git-lfs/git-lfs/releases/download/v3.7.1/git-lfs-linux-amd64-v3.7.1.tar.gz) ## How it works: ![a diagram showing how Git LFS works](https://git-lfs.com/images/graphic.gif) [Git LFS security update: All users should update to 3.7.1.](https://github.com/git-lfs/git-lfs/security/advisories/GHSA-6pvw-g552-53c5) ## Getting Started 1. Download and install the Git command line extension. Once downloaded and installed, set up Git LFS for your user account by running: ``` git lfs install ``` You only need to run this once per user account. 2. In each Git repository where you want to use Git LFS, select the file types you'd like Git LFS to manage (or directly edit your .gitattributes). You can configure additional file extensions at anytime. ``` git lfs track "*.psd" ``` Now make sure .gitattributes is tracked: ``` git add .gitattributes ``` Note that defining the file types Git LFS should track will not, by itself, convert any pre-existing files to Git LFS, such as files on other branches or in your prior commit history. To do that, use the [git lfs migrate(1)](https://github.com/git-lfs/git-lfs/blob/main/docs/man/git-lfs-migrate.adoc?utm_source=gitlfs_site&utm_medium=doc_man_migrate_link&utm_campaign=gitlfs) command, which has a range of options designed to suit various potential use cases. 3. There is no step three. Just commit and push as you normally would; for instance, if your current branch is named `main`: ``` git add file.psd git commit -m "Add design file" git push origin main ``` Check out our [wiki](https://github.com/git-lfs/git-lfs/wiki?utm_source=gitlfs_site&utm_medium=wiki_link&utm_campaign=gitlfs), [discussion forum](https://github.com/git-lfs/git-lfs/discussions?utm_source=gitlfs_site&utm_medium=discussions_link&utm_campaign=gitlfs), and [documentation](https://github.com/git-lfs/git-lfs/tree/main/docs?utm_source=gitlfs_site&utm_medium=docs_link&utm_campaign=gitlfs) for help with any questions you might have\! ## Git LFS is an open source project To start a discussion, file an issue, or contribute to the project, head over [to the repository](https://github.com/git-lfs/git-lfs?utm_source=gitlfs_site&utm_medium=repo_link&utm_campaign=gitlfs) or read our [guide to contributing](https://github.com/git-lfs/git-lfs/blob/main/CONTRIBUTING.md?utm_source=gitlfs_site&utm_medium=contributing_link&utm_campaign=gitlfs). If you're interested in integrating Git LFS into another tool or product, you might want to read the [API specification](https://github.com/git-lfs/git-lfs/blob/main/docs/api/README.md?utm_source=gitlfs_site&utm_medium=api_spec_link&utm_campaign=gitlfs) or check out our [reference server implementation](https://github.com/git-lfs/lfs-test-server?utm_source=gitlfs_site&utm_medium=reference_servedr&utm_campaign=gitlfs). ## Features - ### Large file versioning Version large files—even those as large as a couple GB in size—with Git. - ### More repository space Host more in your Git repositories. External file storage makes it easy to keep your repository at a manageable size. - ### Faster cloning and fetching Download less data. This means faster cloning and fetching from repositories that deal with large files. - ### Same Git workflow Work like you always do on Git—no need for additional commands, secondary storage systems, or toolsets. - ### Same access controls and permissions Keep the same access controls and permissions for large files as the rest of your Git repository when working with a remote host like GitHub. [with by .](https://github.com/?utm_source=gitlfs_site&utm_medium=footer&utm_campaign=gitlfs) Git is a trademark of the [Software Freedom Conservancy](http://sfconservancy.org/).
Readable Markdown	## Getting Started 1. Download and install the Git command line extension. Once downloaded and installed, set up Git LFS for your user account by running: ``` git lfs install ``` You only need to run this once per user account. 2. In each Git repository where you want to use Git LFS, select the file types you'd like Git LFS to manage (or directly edit your .gitattributes). You can configure additional file extensions at anytime. ``` git lfs track "*.psd" ``` Now make sure .gitattributes is tracked: ``` git add .gitattributes ``` Note that defining the file types Git LFS should track will not, by itself, convert any pre-existing files to Git LFS, such as files on other branches or in your prior commit history. To do that, use the [git lfs migrate(1)](https://github.com/git-lfs/git-lfs/blob/main/docs/man/git-lfs-migrate.adoc?utm_source=gitlfs_site&utm_medium=doc_man_migrate_link&utm_campaign=gitlfs) command, which has a range of options designed to suit various potential use cases. 3. There is no step three. Just commit and push as you normally would; for instance, if your current branch is named `main`: ``` git add file.psd git commit -m "Add design file" git push origin main ``` Check out our [wiki](https://github.com/git-lfs/git-lfs/wiki?utm_source=gitlfs_site&utm_medium=wiki_link&utm_campaign=gitlfs), [discussion forum](https://github.com/git-lfs/git-lfs/discussions?utm_source=gitlfs_site&utm_medium=discussions_link&utm_campaign=gitlfs), and [documentation](https://github.com/git-lfs/git-lfs/tree/main/docs?utm_source=gitlfs_site&utm_medium=docs_link&utm_campaign=gitlfs) for help with any questions you might have\! ## Git LFS is an open source project To start a discussion, file an issue, or contribute to the project, head over [to the repository](https://github.com/git-lfs/git-lfs?utm_source=gitlfs_site&utm_medium=repo_link&utm_campaign=gitlfs) or read our [guide to contributing](https://github.com/git-lfs/git-lfs/blob/main/CONTRIBUTING.md?utm_source=gitlfs_site&utm_medium=contributing_link&utm_campaign=gitlfs). If you're interested in integrating Git LFS into another tool or product, you might want to read the [API specification](https://github.com/git-lfs/git-lfs/blob/main/docs/api/README.md?utm_source=gitlfs_site&utm_medium=api_spec_link&utm_campaign=gitlfs) or check out our [reference server implementation](https://github.com/git-lfs/lfs-test-server?utm_source=gitlfs_site&utm_medium=reference_servedr&utm_campaign=gitlfs). ## Features - ### Large file versioning Version large files—even those as large as a couple GB in size—with Git. - ### More repository space Host more in your Git repositories. External file storage makes it easy to keep your repository at a manageable size. - ### Faster cloning and fetching Download less data. This means faster cloning and fetching from repositories that deal with large files. - ### Same Git workflow Work like you always do on Git—no need for additional commands, secondary storage systems, or toolsets. - ### Same access controls and permissions Keep the same access controls and permissions for large files as the rest of your Git repository when working with a remote host like GitHub.
Shard	159 (laksa)
Root Hash	12278960552995301759
Unparsed URL	com,git-lfs!/ s443