Carview!

CARVIEW

MOTORHOMES

Select Language

HTTP/2 302 server: nginx date: Wed, 30 Jul 2025 20:42:39 GMT content-type: text/plain; charset=utf-8 content-length: 0 x-archive-redirect-reason: found capture at 20100102003213 location: https://web.archive.org/web/20100102003213/https://github.com/security server-timing: captures_list;dur=2.479704, exclusion.robots;dur=0.021249, exclusion.robots.policy;dur=0.010462, esindex;dur=0.009496, cdx.remote;dur=145.018226, LoadShardBlock;dur=894.138213, PetaboxLoader3.resolve;dur=187.317895, PetaboxLoader3.datanode;dur=342.250546 x-app-server: wwwb-app219 x-ts: 302 x-tr: 1142 server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0 set-cookie: SERVER=wwwb-app219; path=/ x-location: All x-rl: 0 x-na: 0 x-page-cache: MISS server-timing: MISS x-nid: DigitalOcean referrer-policy: no-referrer-when-downgrade permissions-policy: interest-cohort=() HTTP/2 200 server: nginx date: Wed, 30 Jul 2025 20:42:42 GMT content-type: text/html; charset=utf-8 x-archive-orig-server: nginx/0.7.61 x-archive-orig-date: Sat, 02 Jan 2010 00:32:13 GMT x-archive-orig-connection: close x-archive-orig-status: 200 OK x-archive-orig-etag: "8bb8f8b4dd2592f0fa3642f37626ba56" x-archive-orig-x-runtime: 40ms x-archive-orig-content-length: 8202 x-archive-orig-cache-control: private, max-age=0, must-revalidate x-archive-guessed-content-type: text/html x-archive-guessed-charset: utf-8 memento-datetime: Sat, 02 Jan 2010 00:32:13 GMT link: ; rel="original", ; rel="timemap"; type="application/link-format", ; rel="timegate", ; rel="first memento"; datetime="Sun, 15 Nov 2009 14:42:47 GMT", ; rel="prev memento"; datetime="Sun, 27 Dec 2009 02:16:32 GMT", ; rel="memento"; datetime="Sat, 02 Jan 2010 00:32:13 GMT", ; rel="next memento"; datetime="Thu, 21 Jan 2010 14:09:04 GMT", ; rel="last memento"; datetime="Wed, 30 Jul 2025 08:37:20 GMT" content-security-policy: default-src 'self' 'unsafe-eval' 'unsafe-inline' data: blob: archive.org web.archive.org web-static.archive.org wayback-api.archive.org athena.archive.org analytics.archive.org pragma.archivelab.org wwwb-events.archive.org x-archive-src: TLA-20100102001741-00475-ia360902-c/TLA-20100102002639-00000-ia360906.us.archive.org.warc.gz server-timing: captures_list;dur=4.237482, exclusion.robots;dur=0.130137, exclusion.robots.policy;dur=0.057304, esindex;dur=0.095969, cdx.remote;dur=565.043291, LoadShardBlock;dur=1653.752314, PetaboxLoader3.datanode;dur=711.687155, PetaboxLoader3.resolve;dur=275.992483, load_resource;dur=165.438142 x-app-server: wwwb-app219 x-ts: 200 x-tr: 2726 server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0 x-location: All x-rl: 0 x-na: 0 x-page-cache: MISS server-timing: MISS x-nid: DigitalOcean referrer-policy: no-referrer-when-downgrade permissions-policy: interest-cohort=() content-encoding: gzip Security - GitHub

We know your code is extremely important to you and your business and we're very protective of it. After all, GitHub's code is hosted on GitHub, too!

Physical security measures

GitHub's infrastructure is hosted on Rackspace, a publicly-traded company that's committed to keeping your data secure. They provide us with state-of-the-art servers protected by biometric locks and round-the-clock interior and exterior surveillance monitoring. Only authorized personnel have access to the data center. 24/7/365 onsite staff also provides additional protection against unauthorized entry and security breaches.

Software security measures

In addition to Rackspace's system monitoring, we also employ a team of 24/7/365 server specialists at Anchor Hosting to keep our software and its dependencies up to date eliminating potential security vulnerabilities. They have also setup a wide range of monitoring solutions for preventing and eliminating attacks to the site.

Private code hosted on GitHub can only be accessed over a secure protocol. SSL (https) is used on the site when accessing private repositories and we only allow the transfer of private git data using SSH.

Redundancy

Every piece of hardware we use has an identical copy ready and waiting for an immediate hot-swap in case of hardware or software failure. Every line of code we store is saved on a minimum of three different servers, including an off-site backup just in case a meteor ever hits the Rackspace datacenter (we'll keep our fingers crossed that doesn't happen).

Credit card safety

When you sign up for a paid account on GitHub, we do not store any of your card information on our servers. It's handed off to Braintree Payment Solutions, a company dedicated to storing your sensitive data on PCI-Compliant servers.

Email us for more information

Please use our contact form or support site to get in touch with us and we'll be happy to discuss security with you.

Need to report something?

Please email us immediately at security@github.com, this will go directly to one or more of the GitHub founders and will receive our full attention. If we don't respond immediately, there's a good chance we're trying to fix it first.