Website profiles · Technology insights · Alternatives

gist.github.com No paid content found

Categories: Development

GitHub Gist: instantly share code, notes, and snippets.

Visit website

Updated: 2026-09-24 00:55 Language: English (default) Access: Normal

Profile views 0

Outbound visits 0

Editorial Review

Website Review

What is GitHub Gist?

GitHub Gist is a lightweight service from GitHub for sharing code, notes, and snippets without creating a full repository. You paste a file or a few files, and it immediately gets a shareable URL. Each gist can be public (discoverable and searchable) or secret (unlisted, shared only by link). Gists support version history, comments, stars, and forks, and they can be embedded in other pages.

A practical way to think about it: if you want to show someone 20 lines of config, a one-off script, or a short how-to, a gist is faster than a repo and easier to read than a chat message. The Discover page shows what this looks like in practice — recent examples include a Linux virtual-display guide for headless game streaming, a course setup checklist, an iPhone wallpaper walkthrough, and a project "spec" document with conventions and constraints. That range is the point: gists hold prose and instructions as comfortably as code.

H3 When a gist fits, and when it doesn't

Situation	Gist	Full repository
Sharing a snippet, config, or short note	Good fit	Overkill
Multiple files with folders and build steps	Awkward	Better
Issue tracking, pull requests, CI	Not available	Built in
Quick revision history of one file	Yes	Yes
Public discovery and search	Possible	Possible

Gists are not a replacement for project hosting. They have no real directory structure, no pull-request workflow, and no continuous integration. If your snippet grows into a tool with dependencies, tests, or collaborators making changes, move it to a repository and keep the gist as a pointer.

H3 How people actually use them

Sharing a fix or workaround: write the steps once, send the link instead of re-explaining.
Collecting setup notes: installation lists, environment variables, or onboarding steps for a course or team.
Embedding examples: gists can be embedded in documentation, blogs, or README files.
Drafting: some people draft a document in a gist before moving it somewhere permanent.

For a concrete scenario: you're helping a colleague configure a tool on their machine. Instead of typing commands into chat, create a secret gist with the commands and a short explanation, then send the link. They can comment on specific lines if something fails, and you can edit the gist — the URL stays the same and the revision history shows what changed.

Next step: open GitHub Gist, paste your snippet, choose public or secret, and create it. If you later need collaboration, issues, or automated tests, create a repository instead and link back to the gist.

How do I create and share a new gist?

A gist is a single-file or multi-file snippet hosted on GitHub, with its own URL you can send to anyone. Create one at GitHub Gist by pasting or typing your content, giving the file a name with the right extension, and choosing public or secret visibility.

Creating a gist

Open the gist editor and type or paste your content. The filename matters: setup.sh, notes.md or query.sql tells the viewer how to read it.
Add more files with the "Add file" control if the snippet needs a companion file, such as a script plus a config sample.
Write a short description line. This becomes the page title and is what people see when the gist is linked or searched.
Choose visibility. Public gists appear in Discover and can be found by search engines; secret gists are unlisted and reachable only by URL, but they are not private in a security sense — anyone with the link can read them.
Create the gist, then copy the browser URL. That link is the shareable artifact.

Sharing and revising

Send the URL directly, or embed it where a snippet is useful. Editing later keeps the same URL, so a link you already shared stays valid; older versions remain available in the revision history. Readers can comment, star and fork, which is how the gists shown on the Discover page accumulate the fork, star and comment counts listed beside them.

A practical scenario: you are helping a colleague debug a config file. Rather than pasting a wall of text into chat, create a secret gist with the file named correctly, share the link, and update it as you iterate — they always see the current version.

Choosing visibility and format

Choice	Good for	Trade-off
Public gist	Examples, reusable snippets, guides you want found	Indexed and discoverable; don't include anything sensitive
Secret gist	Quick sharing with a specific person or team	Unlisted, not access-controlled; anyone with the link can read it
Single file	Short snippets, one script	Simplest link, no navigation
Multiple files	A script plus config, or a small guide	Slightly more to maintain, but self-contained

If the material is a real project with issues, collaborators and history, a repository is the better fit; gists are for snippets, notes and one-off guides. Next step: create the gist with a descriptive filename and description, then paste the URL into the message or document where it is needed.

What is the difference between a secret gist and a public gist?

A public gist is discoverable and indexable: it appears in Discover gists, can be searched, and anyone with the URL or a search engine can read it. A secret gist is unlisted: it does not appear in Discover or search results, but anyone who has the link can still read it. "Secret" here means hidden from listings, not access-controlled.

H3 Practical differences

Aspect	Public gist	Secret gist
Listed in Discover/search	Yes	No
Readable by anyone with the URL	Yes	Yes
Suitable for credentials or private data	No	No
Good for sharing snippets in issues, chats, docs	Yes	Yes, when you want a quieter link

Neither option is private in the security sense. If you need real access control, use a private repository or another host rather than a gist.

H3 How to decide

Ask who should be able to find it. If you want the snippet to be searchable and reusable by others, make it public. If you only want to hand the link to specific people and keep it out of listings, choose secret. In both cases, review the content first: remove API keys, tokens, personal data and anything under NDA.

A concrete scenario: a developer writes a short configuration walkthrough and wants other users to find it through search, so a public gist fits. The same developer pastes a one-off debug log for a colleague and does not want it indexed, so a secret gist fits better. The code is identical; only the intended audience changes.

Next step: before creating the gist, scan the file for secrets and decide whether "anyone with the link" is an acceptable audience. If it is not, do not use a gist at all.

Can I edit or delete a gist after publishing it?

Yes. On GitHub Gist, a published gist stays editable, and you can delete it entirely.

Editing: Open the gist, click Edit, change the filename, content, or description, then save. GitHub keeps a revision history, so you can view or restore earlier versions. Edits are immediate for anyone with the link.

Deleting: Open the gist and choose Delete in the page controls, then confirm. Deletion removes the gist and its history. If you fork or copy a gist into a repository first, the copy is separate and is not deleted.

Public vs. secret: Editing works the same way for both. A secret gist is unlisted, not private, so anyone with the URL can read it; deleting is the only way to fully remove it.

Deciding what to do

Situation	Best action
Fix a typo or update a snippet	Edit and save
Replace the content but keep the same URL	Edit and save
Publish something sensitive by mistake	Delete immediately
Keep a copy while removing the original	Fork or copy it, then delete the gist

If you only need to change part of a multi-file gist, edit that file individually rather than recreating the gist, so the URL and stars stay intact.

How do I embed a gist in a blog or website?

To embed a gist, use the <script> tag GitHub provides on the gist page. Open the gist, click "Embed" (or copy the "Embed" URL from the top-right menu), and paste the resulting snippet into your blog's HTML where you want the code to appear.

The snippet looks like this:

<script src="https://gist.github.com/USERNAME/GIST_ID.js"></script>

For a single file from a multi-file gist, append ?file=FILENAME to the .js URL. GitHub also offers a .pibb variant (a styled, iframe-free embed) if you prefer not to load a script.

How it behaves in practice

Rendering: GitHub's script writes an iframe into your page, so the gist's own CSS and line numbers come along. It won't inherit your site's code theme.
WordPress.com and some hosted platforms: These often strip <script> tags. Use the .pibb URL in a Custom HTML block, or paste the gist URL on its own line if your editor supports oEmbed.
Static site generators: Most (Jekyll, Hugo, Eleventy) render raw HTML in Markdown, so the script tag works. If your Markdown processor escapes HTML, wrap it in a shortcode or a raw-HTML block.
Performance: Each embed is a separate request. A page with many gists will make many calls; consider linking to the gist instead when the code is secondary.

When to choose what

Situation	Best option
Blog with full HTML control	Standard `.js` script embed
Platform blocks scripts	`.pibb` URL or oEmbed
Only one file of many	Add `?file=` parameter
Code is long or incidental	Link to the gist instead

Next step: Create a test post with one gist embed, view it on mobile and desktop, and check whether the iframe width and height suit your layout. If it overflows, add CSS to your theme targeting .gist or the iframe.

For a working example of how people publish guides and snippets this way, browse GitHub Gist.

Is there a size or file limit for gists?

GitHub Gist is built for small, shareable text: code, notes, snippets, and short guides. It is not a file-hosting service, so treat it as a place for material you would paste into a message or a README rather than a place to park large binaries.

What the page shows in practice

The gists surfaced on Discover gists are almost all single files, and the visible ones are text: a Linux virtual-display guide, a course setup list, an iPhone wallpaper walkthrough, a spec example, and a VPN note. Several have collected comments, forks and stars while remaining a single file. That pattern tells you more about intended use than any hard number: gists work best when the content is a document, not an archive.

Practical limits to plan around

Gist itself. GitHub's own documentation states a per-file size limit for gists (currently 100 MB per file) and notes that larger files are truncated in the web interface. That is a ceiling, not a target — a gist near it will be awkward to read, diff or clone.
Git-backed storage. Because each gist is a Git repository, a gist can hold multiple files, and a revision history accumulates. Old versions of large files stay in that history, so a gist that once held a big file stays heavy even after you delete it.
Rendering and review. Markdown, code and small data files display inline and can be commented on line by line. Binaries, images and large logs do not get that treatment, which is why the examples above are all text.

Choosing between a gist and a repository

Situation	Better fit
One snippet, note or short guide you want to link to	Gist
A handful of related small text files	Gist, using multiple files
Full project with issues, pull requests and CI	A regular repository
Images, videos, datasets, build artifacts	A repository with releases, or dedicated file storage

A concrete scenario

Suppose you want to share a 4K streaming setup guide, like the NVIDIA virtual-display gist in the discovery list. A single Markdown file with headings, commands and a note about the hardware it was tested on fits perfectly, and readers can comment on specific lines. If you later want to attach screenshots, sample configs and a changelog, split the text into a few files in the same gist — or move to a repository once you need issues and pull requests.

Next step

Before publishing, check two things: that no single file is close to the per-file limit, and that nothing you paste in — API keys, tokens, personal data — is meant to stay private. Gists are easy to create and easy to forget, so delete or update the ones you no longer want discoverable.

First, clear up the word "code"

The keyword "code" is overloaded, and that causes real confusion for developers:

Postal code — the ZIP Code (U.S.) or postal code (Canada) that identifies a delivery area.
API key — the credential you use to authenticate your requests. It is not postal data.
Source code — the program you write to call the API.

When someone searches for "postal code API code," they usually want example request/response code for a postal code service. The rest of this article treats it that way.

What a postal code API actually returns

Response fields vary by provider and endpoint, but the core set is fairly consistent. A single-code lookup commonly returns:

Field	Example	Notes
Postal code	`90210`	The code you queried
City	`Beverly Hills`	May be one of several acceptable place names
State / Province	`CA`	Two-letter abbreviation
County	`Los Angeles`	Useful for tax, territory, and reporting logic
Latitude / Longitude	`34.0901, -118.4065`	Usually the centroid of the area
ZIP+4	`90210-1234`	Present only when a specific delivery segment is known
Time zone	`America/Los_Angeles`	Helps with scheduling and display
Area codes	`310`, `424`	Regional phone context

Richer datasets add 90+ fields: boundaries, population, income, elevation, and more. You rarely need all of them — request only what your application uses.

A representative JSON response

{
  "postal_code": "90210",
  "city": "Beverly Hills",
  "state": "CA",
  "county": "Los Angeles",
  "latitude": 34.0901,
  "longitude": -118.4065,
  "timezone": "America/Los_Angeles",
  "area_codes": ["310", "424"]
}

XML responses carry the same information in tag form. Choose based on what your stack parses most easily; JSON is the common default.

Common request patterns

Most postal code APIs support four patterns. Knowing which one you need prevents wasted calls.

1. Lookup by code

You have a code and want its details. This is the simplest and fastest call.

GET /lookup?code=90210

2. Reverse lookup by address

You have a street address and want to confirm or complete the code. This is the pattern behind checkout address validation.

GET /validate?street=...&city=...&state=...

3. Radius search

You have a center point and want all codes within a distance. Useful for store locators and delivery zones.

GET /radius?code=90210&miles=10

4. Batch validation

You have a file of addresses and want them cleaned in bulk. Batch endpoints trade latency for throughput and usually have their own limits.

Handling missing and ambiguous matches

Real data is messy. Plan for these cases:

No match — the code doesn't exist or the address is malformed. Return a clear error rather than a silent empty object.
Multiple matches — a city name may map to several codes, or a code may span several acceptable city names. Decide whether to pick the primary or return a list.
Partial match — the street is valid but the ZIP+4 isn't. Fall back to the 5-digit code.
Stale data — codes are added, retired, and reassigned. Refresh your dataset on a regular schedule.

A practical rule: validate at the point of entry, store the normalized result, and never re-derive it later from raw user input.

Practical use cases

Checkout address validation — catch typos before shipping, reduce failed deliveries.
Shipping zone lookup — map a code to a zone, carrier route, or rate table.
Data enrichment — append county, coordinates, or demographics to existing records.
Store and service locators — radius search to find nearby branches or coverage areas.
Territory and tax logic — county and boundary data drive jurisdiction rules.

Licensing and data-source considerations

Postal code data originates with national authorities — USPS in the United States and Canada Post in Canada. Providers license and repackage it, which is why accuracy, update frequency, and field coverage differ between services. Before committing:

Confirm the data source and how often it refreshes.
Check whether ZIP+4 and boundary data are included or sold separately.
Review usage limits and whether batch processing is allowed.
Read the license terms for redistribution and storage.

Pricing and plan details change, so check the provider's current documentation rather than relying on secondhand figures.

Getting started

Decide which request pattern you need (lookup, reverse, radius, or batch).
Pick the fields you'll actually store.
Write a small test call and inspect the raw response.
Add error handling for no-match and ambiguous cases.
Cache results where the same codes repeat.

A postal code API is ultimately a translation layer: you give it a code or an address, and it gives back structured location facts. Understand the fields, match them to your use case, and handle the messy edges — that's most of the work.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality.

Domain and Registration

Registered in 2007, this domain has about 18 years of history. That suggests continuity, although ownership and purpose may have changed. The registrar, MarkMonitor Inc., specializes in corporate domain and brand management, suggesting attention to domain asset protection. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The domain uses the common .com extension, which is not an independent safety signal.

DNS and Email

The lowest TTL is 14 seconds, supporting rapid record changes at the cost of more frequent lookups. Nameservers are provided by Amazon Route 53, indicating managed DNS hosting. MX records point to the Microsoft 365 email service. CAA records restrict which certificate authorities are authorized to issue certificates. SPF and DMARC are configured. DKIM status is unknown.

TLS and Certificates

The certificate issuer is Sectigo Limited, a commercial certificate authority. The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: Permissions-Policy. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. No obvious internal addresses or debug information were found in the headers. The Server header contains the custom value github.com. No explicit CDN or WAF marker was found in the response headers.

Technology Stack Analysis

The public page identifies React without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. Twitter Card metadata is configured. The title has 23 characters, within a common display range. A meta description is present, with 55 characters. The observed directives allow indexing and link following.

Hosting and Email

DNSAmazon Route 53

Hostinggithub.com

EmailMicrosoft 365

Location United States 140.82.114.3

User reviews (0)

No reviews yet.

Pages, Search and Sharing

Meta description	GitHub Gist: instantly share code, notes, and snippets.
Canonical URL	Not detected
Language	English (default)
Twitter Card	summary_large_image

Social Sharing Preview

11 fields

Sharing metadata

og:type	website
og:image	https://github.com/opengraph.png
og:title	Discover gists
og:image:alt	GitHub Gist: instantly share code, notes, and snippets.
og:site_name	Gist
og:description	GitHub Gist: instantly share code, notes, and snippets.
twitter:card	summary_large_image
twitter:site	@github
twitter:image	https://github.com/opengraph.png
twitter:title	Discover gists
twitter:description	GitHub Gist: instantly share code, notes, and snippets.

robots.txt (opens in a new tab)

662 rules

gptbot 12 allowed · 72 disallowed

/$
/about
/customer-stories
/enterprise
/features
/marketplace
/mcp
/newsroom
/pricing
/resources
/security
/solutions
/*/*/pulse
/*/*/projects
/*/*/forks
/*/*/issues/new
/*/*/milestones/new
/*/*/issues/search
/*/*/commits/
/*/*/branches
/*/*/contributors
/*/*/tags
/*/*/stargazers
/*/*/watchers
/*/*/network
/*/*/graphs
/*/*/compare
/*/tree/
/gist/
/*/download
/*/revisions
/*/commits/*?author
/*/commits/*?path
/*/comments
/*/archive/
/*/blame/
/*/raw/
/*/cache/
/.git/
*/.git/
/*.git$
/search/advanced
/search$
/*.atom$
/ekansa/Open-Context-Data
/ekansa/opencontext-*
*/tarball/
*/zipball/
/*commits?author=*
/*report-abuse?report=*
/account-login
/Explodingstuff/
/copilot/
/copilot/c/
/*?source=*
/*&source=*
/*?ref_cta=*
/*&ref_cta=*
/*?plan=*
/*&plan=*
/*?return_to=*
/*&return_to=*
/*?ref_loc=*
/*&ref_loc=*
/*?setup_organization=*
/*&setup_organization=*
/*?source_repo=*
/*&source_repo=*
/*?ref_page=*
/*&ref_page=*
/*?referrer=*
/*&referrer=*
/*?report=*
/*&report=*
/*?author=*
/*&author=*
/*?since=*
/*&since=*
/*?until=*
/*&until=*
/*?tab=*
/*&tab=*
/*?q=*
/*&q=*
IntervalCrawl delay 1 seconds

oai-searchbot 12 allowed · 72 disallowed

/$
/about
/customer-stories
/enterprise
/features
/marketplace
/mcp
/newsroom
/pricing
/resources
/security
/solutions
/*/*/pulse
/*/*/projects
/*/*/forks
/*/*/issues/new
/*/*/milestones/new
/*/*/issues/search
/*/*/commits/
/*/*/branches
/*/*/contributors
/*/*/tags
/*/*/stargazers
/*/*/watchers
/*/*/network
/*/*/graphs
/*/*/compare
/*/tree/
/gist/
/*/download
/*/revisions
/*/commits/*?author
/*/commits/*?path
/*/comments
/*/archive/
/*/blame/
/*/raw/
/*/cache/
/.git/
*/.git/
/*.git$
/search/advanced
/search$
/*.atom$
/ekansa/Open-Context-Data
/ekansa/opencontext-*
*/tarball/
*/zipball/
/*commits?author=*
/*report-abuse?report=*
/account-login
/Explodingstuff/
/copilot/
/copilot/c/
/*?source=*
/*&source=*
/*?ref_cta=*
/*&ref_cta=*
/*?plan=*
/*&plan=*
/*?return_to=*
/*&return_to=*
/*?ref_loc=*
/*&ref_loc=*
/*?setup_organization=*
/*&setup_organization=*
/*?source_repo=*
/*&source_repo=*
/*?ref_page=*
/*&ref_page=*
/*?referrer=*
/*&referrer=*
/*?report=*
/*&report=*
/*?author=*
/*&author=*
/*?since=*
/*&since=*
/*?until=*
/*&until=*
/*?tab=*
/*&tab=*
/*?q=*
/*&q=*
IntervalCrawl delay 1 seconds

claudebot 12 allowed · 72 disallowed

/$
/about
/customer-stories
/enterprise
/features
/marketplace
/mcp
/newsroom
/pricing
/resources
/security
/solutions
/*/*/pulse
/*/*/projects
/*/*/forks
/*/*/issues/new
/*/*/milestones/new
/*/*/issues/search
/*/*/commits/
/*/*/branches
/*/*/contributors
/*/*/tags
/*/*/stargazers
/*/*/watchers
/*/*/network
/*/*/graphs
/*/*/compare
/*/tree/
/gist/
/*/download
/*/revisions
/*/commits/*?author
/*/commits/*?path
/*/comments
/*/archive/
/*/blame/
/*/raw/
/*/cache/
/.git/
*/.git/
/*.git$
/search/advanced
/search$
/*.atom$
/ekansa/Open-Context-Data
/ekansa/opencontext-*
*/tarball/
*/zipball/
/*commits?author=*
/*report-abuse?report=*
/account-login
/Explodingstuff/
/copilot/
/copilot/c/
/*?source=*
/*&source=*
/*?ref_cta=*
/*&ref_cta=*
/*?plan=*
/*&plan=*
/*?return_to=*
/*&return_to=*
/*?ref_loc=*
/*&ref_loc=*
/*?setup_organization=*
/*&setup_organization=*
/*?source_repo=*
/*&source_repo=*
/*?ref_page=*
/*&ref_page=*
/*?referrer=*
/*&referrer=*
/*?report=*
/*&report=*
/*?author=*
/*&author=*
/*?since=*
/*&since=*
/*?until=*
/*&until=*
/*?tab=*
/*&tab=*
/*?q=*
/*&q=*
IntervalCrawl delay 1 seconds

anthropic-ai 12 allowed · 72 disallowed

/$
/about
/customer-stories
/enterprise
/features
/marketplace
/mcp
/newsroom
/pricing
/resources
/security
/solutions
/*/*/pulse
/*/*/projects
/*/*/forks
/*/*/issues/new
/*/*/milestones/new
/*/*/issues/search
/*/*/commits/
/*/*/branches
/*/*/contributors
/*/*/tags
/*/*/stargazers
/*/*/watchers
/*/*/network
/*/*/graphs
/*/*/compare
/*/tree/
/gist/
/*/download
/*/revisions
/*/commits/*?author
/*/commits/*?path
/*/comments
/*/archive/
/*/blame/
/*/raw/
/*/cache/
/.git/
*/.git/
/*.git$
/search/advanced
/search$
/*.atom$
/ekansa/Open-Context-Data
/ekansa/opencontext-*
*/tarball/
*/zipball/
/*commits?author=*
/*report-abuse?report=*
/account-login
/Explodingstuff/
/copilot/
/copilot/c/
/*?source=*
/*&source=*
/*?ref_cta=*
/*&ref_cta=*
/*?plan=*
/*&plan=*
/*?return_to=*
/*&return_to=*
/*?ref_loc=*
/*&ref_loc=*
/*?setup_organization=*
/*&setup_organization=*
/*?source_repo=*
/*&source_repo=*
/*?ref_page=*
/*&ref_page=*
/*?referrer=*
/*&referrer=*
/*?report=*
/*&report=*
/*?author=*
/*&author=*
/*?since=*
/*&since=*
/*?until=*
/*&until=*
/*?tab=*
/*&tab=*
/*?q=*
/*&q=*
IntervalCrawl delay 1 seconds

perplexitybot 12 allowed · 72 disallowed

/$
/about
/customer-stories
/enterprise
/features
/marketplace
/mcp
/newsroom
/pricing
/resources
/security
/solutions
/*/*/pulse
/*/*/projects
/*/*/forks
/*/*/issues/new
/*/*/milestones/new
/*/*/issues/search
/*/*/commits/
/*/*/branches
/*/*/contributors
/*/*/tags
/*/*/stargazers
/*/*/watchers
/*/*/network
/*/*/graphs
/*/*/compare
/*/tree/
/gist/
/*/download
/*/revisions
/*/commits/*?author
/*/commits/*?path
/*/comments
/*/archive/
/*/blame/
/*/raw/
/*/cache/
/.git/
*/.git/
/*.git$
/search/advanced
/search$
/*.atom$
/ekansa/Open-Context-Data
/ekansa/opencontext-*
*/tarball/
*/zipball/
/*commits?author=*
/*report-abuse?report=*
/account-login
/Explodingstuff/
/copilot/
/copilot/c/
/*?source=*
/*&source=*
/*?ref_cta=*
/*&ref_cta=*
/*?plan=*
/*&plan=*
/*?return_to=*
/*&return_to=*
/*?ref_loc=*
/*&ref_loc=*
/*?setup_organization=*
/*&setup_organization=*
/*?source_repo=*
/*&source_repo=*
/*?ref_page=*
/*&ref_page=*
/*?referrer=*
/*&referrer=*
/*?report=*
/*&report=*
/*?author=*
/*&author=*
/*?since=*
/*&since=*
/*?until=*
/*&until=*
/*?tab=*
/*&tab=*
/*?q=*
/*&q=*
IntervalCrawl delay 1 seconds

bytespider 0 allowed · 1 disallowed

adsbot-google 0 allowed · 72 disallowed

/*/*/pulse
/*/*/projects
/*/*/forks
/*/*/issues/new
/*/*/milestones/new
/*/*/issues/search
/*/*/commits/
/*/*/branches
/*/*/contributors
/*/*/tags
/*/*/stargazers
/*/*/watchers
/*/*/network
/*/*/graphs
/*/*/compare
/*/tree/
/gist/
/*/download
/*/revisions
/*/commits/*?author
/*/commits/*?path
/*/comments
/*/archive/
/*/blame/
/*/raw/
/*/cache/
/.git/
*/.git/
/*.git$
/search/advanced
/search$
/*.atom$
/ekansa/Open-Context-Data
/ekansa/opencontext-*
*/tarball/
*/zipball/
/*commits?author=*
/*report-abuse?report=*
/account-login
/Explodingstuff/
/copilot/
/copilot/c/
/*?source=*
/*&source=*
/*?ref_cta=*
/*&ref_cta=*
/*?plan=*
/*&plan=*
/*?return_to=*
/*&return_to=*
/*?ref_loc=*
/*&ref_loc=*
/*?setup_organization=*
/*&setup_organization=*
/*?source_repo=*
/*&source_repo=*
/*?ref_page=*
/*&ref_page=*
/*?referrer=*
/*&referrer=*
/*?report=*
/*&report=*
/*?author=*
/*&author=*
/*?since=*
/*&since=*
/*?until=*
/*&until=*
/*?tab=*
/*&tab=*
/*?q=*
/*&q=*

adsbot-google-mobile 0 allowed · 72 disallowed

/*/*/pulse
/*/*/projects
/*/*/forks
/*/*/issues/new
/*/*/milestones/new
/*/*/issues/search
/*/*/commits/
/*/*/branches
/*/*/contributors
/*/*/tags
/*/*/stargazers
/*/*/watchers
/*/*/network
/*/*/graphs
/*/*/compare
/*/tree/
/gist/
/*/download
/*/revisions
/*/commits/*?author
/*/commits/*?path
/*/comments
/*/archive/
/*/blame/
/*/raw/
/*/cache/
/.git/
*/.git/
/*.git$
/search/advanced
/search$
/*.atom$
/ekansa/Open-Context-Data
/ekansa/opencontext-*
*/tarball/
*/zipball/
/*commits?author=*
/*report-abuse?report=*
/account-login
/Explodingstuff/
/copilot/
/copilot/c/
/*?source=*
/*&source=*
/*?ref_cta=*
/*&ref_cta=*
/*?plan=*
/*&plan=*
/*?return_to=*
/*&return_to=*
/*?ref_loc=*
/*&ref_loc=*
/*?setup_organization=*
/*&setup_organization=*
/*?source_repo=*
/*&source_repo=*
/*?ref_page=*
/*&ref_page=*
/*?referrer=*
/*&referrer=*
/*?report=*
/*&report=*
/*?author=*
/*&author=*
/*?since=*
/*&since=*
/*?until=*
/*&until=*
/*?tab=*
/*&tab=*
/*?q=*
/*&q=*

bingbot 0 allowed · 8 disallowed

/ekansa/Open-Context-Data
/ekansa/opencontext-*
/account-login
*/tarball/
*/zipball/
/Explodingstuff/
/copilot/
/copilot/c/

adidxbot 0 allowed · 8 disallowed

/ekansa/Open-Context-Data
/ekansa/opencontext-*
/account-login
*/tarball/
*/zipball/
/Explodingstuff/
/copilot/
/copilot/c/

bingpreview 0 allowed · 8 disallowed

/ekansa/Open-Context-Data
/ekansa/opencontext-*
/account-login
*/tarball/
*/zipball/
/Explodingstuff/
/copilot/
/copilot/c/

baidu 0 allowed · 0 disallowed

IntervalCrawl delay 1 seconds

All bots 1 allowed · 72 disallowed

/*?tab=achievements&achievement=*
/*/*/pulse
/*/*/projects
/*/*/forks
/*/*/issues/new
/*/*/milestones/new
/*/*/issues/search
/*/*/commits/
/*/*/branches
/*/*/contributors
/*/*/tags
/*/*/stargazers
/*/*/watchers
/*/*/network
/*/*/graphs
/*/*/compare
/*/tree/
/gist/
/*/download
/*/revisions
/*/commits/*?author
/*/commits/*?path
/*/comments
/*/archive/
/*/blame/
/*/raw/
/*/cache/
/.git/
*/.git/
/*.git$
/search/advanced
/search$
/*.atom$
/ekansa/Open-Context-Data
/ekansa/opencontext-*
*/tarball/
*/zipball/
/*commits?author=*
/*report-abuse?report=*
/account-login
/Explodingstuff/
/copilot/
/copilot/c/
/*?source=*
/*&source=*
/*?ref_cta=*
/*&ref_cta=*
/*?plan=*
/*&plan=*
/*?return_to=*
/*&return_to=*
/*?ref_loc=*
/*&ref_loc=*
/*?setup_organization=*
/*&setup_organization=*
/*?source_repo=*
/*&source_repo=*
/*?ref_page=*
/*&ref_page=*
/*?referrer=*
/*&referrer=*
/*?report=*
/*&report=*
/*?author=*
/*&author=*
/*?since=*
/*&since=*
/*?until=*
/*&until=*
/*?tab=*
/*&tab=*
/*?q=*
/*&q=*

Sitemaps

No sitemaps found

Registration details RDAP / WHOIS

Registrar	MarkMonitor Inc.
Registered	2007-10-09
Expires	2028-10-09
Domain status	client delete prohibited、client transfer prohibited、client update prohibited
Nameservers	dns1.p08.nsone.net、dns2.p08.nsone.net、dns3.p08.nsone.net、dns4.p08.nsone.net、ns-1283.awsdns-32.org、ns-1707.awsdns-21.co.uk、ns-421.awsdns-52.com、ns-520.awsdns-01.net
DNSSEC	unsigned

DNS records

Type	Name	Value	TTL	Priority
A	github.com	140.82.114.3	14	—
MX	github.com	github-com.mail.protection.outlook.com	132	0
NS	github.com	dns1.p08.nsone.net	1186	—
NS	github.com	dns2.p08.nsone.net	1186	—
NS	github.com	dns3.p08.nsone.net	1186	—
NS	github.com	dns4.p08.nsone.net	1186	—
NS	github.com	ns-1283.awsdns-32.org	1186	—
NS	github.com	ns-1707.awsdns-21.co.uk	1186	—
NS	github.com	ns-421.awsdns-52.com	1186	—
NS	github.com	ns-520.awsdns-01.net	1186	—
TXT	github.com	00Dd0000000hHE0=1TBKg000000TN2r	39	—
TXT	github.com	MS=6BF03E6AF5CB689E315FB6199603BABF2C88D805	39	—
TXT	github.com	MS=ms44452932	39	—
TXT	github.com	MS=ms58704441	39	—
TXT	github.com	TAILSCALE-xOzoDvFUzZr5YYVCQFuD	39	—
TXT	github.com	adobe-idp-site-verification=b92c9e999aef825edc36e0a3d847d2dbad5b2fc0e05c79ddd7a16139b48ecf4b	39	—
TXT	github.com	anthropic-domain-verification-4az7qn=if8YWuRRqwLycGJDooumzHtxm	39	—
TXT	github.com	apple-domain-verification=RyQhdzTl6Z6x8ZP4	39	—
TXT	github.com	atlassian-domain-verification=jjgw98AKv2aeoYFxiL/VFaoyPkn3undEssTRuMg6C/3Fp/iqhkV4HVV7WjYlVeF8	39	—
TXT	github.com	calendly-site-verification=at0DQARi7IZvJtXQAWhMqpmIzpvoBNF7aam5VKKxP	39	—
TXT	github.com	cursor-domain-verification-gtfwmt=1rfLOtiTngX5QSxD5HvNKTvm3	39	—
TXT	github.com	docusign=087098e3-3d46-47b7-9b4e-8a23028154cd	39	—
TXT	github.com	facebook-domain-verification=39xu4jzl7roi7x0n93ldkxjiaarx50	39	—
TXT	github.com	google-site-verification=82Le34Flgtd15ojYhHlGF_6g72muSjamlMVThBOJpks	39	—
TXT	github.com	google-site-verification=UTM-3akMgubp6tQtgEuAkYNYLyYAvpTnnSrDMWoDR3o	39	—
TXT	github.com	jamf-site-verification=XtaPNIYghF_e_xRDI8CjgQ	39	—
TXT	github.com	krisp-domain-verification=ZlyiK7XLhnaoUQb2hpak1PLY7dFkl1WE	39	—
TXT	github.com	loom-site-verification=f3787154f1154b7880e720a511ea664d	39	—
TXT	github.com	miro-verification=d2e174fdb00c71e0bcf58f8e58c3da2dd80dcfa9	39	—
TXT	github.com	openai-domain-verification=dv-3nh33eQwdkotMIAzLrIDVZo1	39	—
TXT	github.com	serval-domain-verification-ydryhj=qbkiEakpwEpTvHh5fIiCqtaue	39	—
TXT	github.com	shopify-verification-code=t1YPwcmvnxZyBycaCpk1MPyWoFs72o	39	—
TXT	github.com	stripe-verification=f88ef17321660a01bab1660454192e014defa29ba7b8de9633c69d6b4912217f	39	—
TXT	github.com	v=spf1 ip4:192.30.252.0/22 include:spf.protection.outlook.com include:_netblocks.google.com include:_netblocks2.google.com include:mail.zendesk.com include:_spf.salesforce.com include:servers.mcsv.net include:mktomail.com include:sendgrid.net ip4:62.253.227.114 ip4:166.78.69.169 ip4:166.78.69.170 ip4:166.78.71.131 ~all	39	—
CNAME	gist.github.com	github.com	3600	—
CAA	github.com	0 issue "digicert.com"	3600	—
CAA	github.com	0 issue "globalsign.com"	3600	—
CAA	github.com	0 issue "letsencrypt.org"	3600	—
CAA	github.com	0 issue "sectigo.com"	3600	—
CAA	github.com	0 issuewild "digicert.com"	3600	—
CAA	github.com	0 issuewild "letsencrypt.org"	3600	—
CAA	github.com	0 issuewild "sectigo.com"	3600	—
DMARC	_dmarc.github.com	v=DMARC1; p=quarantine; sp=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1	300	—

TLS and certificates

Assessment	Normal configuration
Supported protocols	TLSv1.2、TLSv1.3
Negotiated protocol	TLSv1.3
Certificate subject	*.github.com
Issuer	Sectigo Limited
Valid until	2026-11-27T23:59 · Remaining when checked: 64 days
Verification details	Certificate trust: Passed · Hostname match: Passed

HTTP response headers

Header	Value
content-type	text/html; charset=utf-8
cache-control	max-age=0, private, must-revalidate
server	github.com
strict-transport-security	max-age=31536000; includeSubdomains; preload
content-security-policy	default-src 'none'; base-uri 'self'; child-src github.githubassets.com github.com/assets-cdn/worker/ github.com/assets/ gist.github.com/assets-cdn/worker/; connect-src 'self' uploads.github.com www.githubstatus.com collector.github.com raw.githubusercontent.com api.github.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com .rel.tunnels.api.visualstudio.com wss://.rel.tunnels.api.visualstudio.com github.githubassets.com objects-origin.githubusercontent.com copilot-proxy.githubusercontent.com proxy.individual.githubcopilot.com proxy.business.githubcopilot.com proxy.enterprise.githubcopilot.com .actions.githubusercontent.com wss://.actions.githubusercontent.com productionresultssa0.blob.core.windows.net productionresultssa1.blob.core.windows.net productionresultssa2.blob.core.windows.net productionresultssa3.blob.core.windows.net productionresultssa4.blob.core.windows.net productionresultssa5.blob.core.windows.net productionresultssa6.blob.core.windows.net productionresultssa7.blob.core.windows.net productionresultssa8.blob.core.windows.net productionresultssa9.blob.core.windows.net productionresultssa10.blob.core.windows.net productionresultssa11.blob.core.windows.net productionresultssa12.blob.core.windows.net productionresultssa13.blob.core.windows.net productionresultssa14.blob.core.windows.net productionresultssa15.blob.core.windows.net productionresultssa16.blob.core.windows.net productionresultssa17.blob.core.windows.net productionresultssa18.blob.core.windows.net productionresultssa19.blob.core.windows.net github-production-repository-image-32fea6.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com insights.github.com wss://alive.github.com wss://alive-staging.github.com api.githubcopilot.com api.individual.githubcopilot.com api.business.githubcopilot.com api.enterprise.githubcopilot.com wss://production-copilot-host.webpubsub.azure.com api.github.com/cmc_internal/api/; font-src github.githubassets.com; form-action 'self' github.com gist.github.com copilot-workspace.githubnext.com objects-origin.githubusercontent.com; frame-ancestors 'none'; frame-src viewscreen.githubusercontent.com notebooks.githubusercontent.com; img-src 'self' data: blob: github.githubassets.com media.githubusercontent.com camo.githubusercontent.com identicons.github.com avatars.githubusercontent.com private-avatars.githubusercontent.com github-cloud.s3.amazonaws.com objects.githubusercontent.com release-assets.githubusercontent.com secured-user-images.githubusercontent.com user-images.githubusercontent.com private-user-images.githubusercontent.com opengraph.githubassets.com repository-images.githubusercontent.com marketplace-screenshots.githubusercontent.com copilotprodattachments.blob.core.windows.net/github-production-copilot-attachments/ github-production-user-asset-6210df.s3.amazonaws.com customer-stories-feed.github.com spotlights-feed.github.com explore-feed.github.com .googleusercontent.com objects-origin.githubusercontent.com .githubusercontent.com; manifest-src 'self'; media-src github.com user-images.githubusercontent.com secured-user-images.githubusercontent.com private-user-images.githubusercontent.com github-production-user-asset-6210df.s3.amazonaws.com gist.github.com github.githubassets.com; script-src github.githubassets.com 'sha256-tSjmyPUky1KbRZ0fw9VUil3wFEbeM82rtbJDygGJAXw='; style-src 'unsafe-inline' github.githubassets.com; upgrade-insecure-requests; worker-src github.githubassets.com github.com/assets-cdn/worker/ github.com/assets/ gist.github.com/assets-cdn/worker/
x-frame-options	deny
x-content-type-options	nosniff
referrer-policy	origin-when-cross-origin, strict-origin-when-cross-origin

Identified technologies

React

Recent Updates

Website images2026-09-24 01:08
Screenshots2026-09-24 01:08