check web redirect url status code checker

Check server response of

Server response
NS records
Whois domain
Response headers
Request headers
Raw HTML code
301 Moved Permanently - cs291.com
HTTP Status: 301
User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])
Connection: keep-alive
Content-Length: 162
Server: GitHub.com
Content-Type: text/html
Location: https://cs291.com/
X-GitHub-Request-Id: AE86:E67AF:59360C:59EBEA:6812577B
Accept-Ranges: bytes
Age: 0
Date: Wed, 30 Apr 2025 17:01:47 GMT
Via: 1.1 varnish
X-Served-By: cache-hel1410024-HEL
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1746032507.465590,VS0,VE122
Vary: Accept-Encoding
X-Fastly-Request-ID: 2a01745cabcba4916c58774fd4fbb120c5db218b

HTTP Code 301 Moved Permanently

301 status code means that the requested resource has been permanently moved to a new URL. All future requests should use the new address.

When is Code 301 used?

  • When changing a website domain
  • When modifying URL structures
  • When setting up redirects for SEO

What does Code 301 mean for the user?

The browser will automatically redirect the user to the new address, and search engines will update their indexes.

200 OK - https://cs291.com/
HTTP Status: 200
User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])
Connection: keep-alive
Content-Length: 20373
Server: GitHub.com
Content-Type: text/html; charset=utf-8
Last-Modified: Tue, 03 Dec 2024 19:34:59 GMT
Access-Control-Allow-Origin: *
ETag: "674f5d63-4f95"
expires: Wed, 30 Apr 2025 17:11:47 GMT
Cache-Control: max-age=600
x-proxy-cache: MISS
X-GitHub-Request-Id: 1F79:72B22:5764FA:581AC6:6812577B
Accept-Ranges: bytes
Age: 0
Date: Wed, 30 Apr 2025 17:01:47 GMT
Via: 1.1 varnish
X-Served-By: cache-hel1410029-HEL
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1746032508.622943,VS0,VE145
Vary: Accept-Encoding
X-Fastly-Request-ID: d1e301a07815456738509c973610c90f20f94a51

HTTP Code 200 OK

200 status code is a standard successful HTTP server response. It means that the client’s request (e.g., from a browser) was successfully processed, and the server is delivering the requested data.

When is Code 200 used?

  • When loading a web page
  • When successfully receiving an API response
  • When processing a form or another HTTP request

What does Code 200 mean for the user?

The user receives content without errors, and the page or application functions properly. If Code 200 is accompanied by data, the browser or program processes and displays it to the user.

GET / HTTP/1.1
Host: cs291.com
Accept: */*
User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])

<!DOCTYPE html>
<html lang="en">

  <head>
    <meta charset="UTF-8">
    <title>Scalable Internet Services</title>
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <link href="/css/theme.css" rel="stylesheet">
    <link href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css" rel="stylesheet">
    <link rel="icon" href="data:;base64,iVBORw0KGgo=">
  </head>

  <body>

        <div class="container-fluid">
      <div class="row-fluid">
        <div class="navbar navbar-inverse navbar-fixed-top" role="navigation">
          <div class="navbar-header">
            <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
              <span class="sr-only">Toggle navigation</span>
              <span class="icon-bar"></span>
              <span class="icon-bar"></span>
              <span class="icon-bar"></span>
            </button>
            <a class="navbar-brand" href="/">Scalable Internet Services</a>
          </div>
          <div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
            <ul class="nav navbar-nav">
              <li class="active"><a href="/schedule/">Class Schedule</a></li>
              <li class="active"><a href="/project0/">Project 0</a></li>
              <li class="active"><a href="/project1/">Project 1</a></li>
              <li class="active"><a href="/project2/">Project 2</a></li>
              <li class="active"><a href="/project3/">Project 3</a></li>
              <li class="active"><a href="/project/">Primary Project</a></li></ul>
          </div>
        </div>
      </div>
    </div>


    <div class="container container-left">
      <div class="row">
        <div class="col-md-3">
          <div class="sidebar">
  <h1 id="course-info">Course Info</h1>

<ul>
  <li>Course Number: CS291A</li>
  <li>Quarter: Fall 2024</li>
</ul>

<h2 id="instructor">Instructor</h2>

<ul>
  <li><a href="https://www.linkedin.com/in/zachary-walker-6a219059/">Zach Walker</a></li>
  <li><a href="mailto:[email protected]">email</a></li>
</ul>

<h2 id="ucsb-ta">UCSB TA</h2>

<ul>
  <li>TBD</li>
</ul>

<h2 id="appfolio-ta">Appfolio TA</h2>

<ul>
  <li>Maximilian Medearis</li>
  <li><a href="mailto:[email protected]">email</a></li>
</ul>

<p>Please use <a href="https://piazza.com/ucsb/fall2024/cs291a">Piazza</a> for class-related correspondance.</p>

<h2 id="dates">Dates</h2>

<h3 id="classes">Classes</h3>

<ul>
  <li>Tues and Thurs</li>
  <li>9:00am – 10:50am PT</li>
  <li>Phelps 3526</li>
</ul>

<h3 id="office-hours">Office Hours</h3>

<!-- - TBD

In-person

- Tuesday 8am -- 9am, Phelps 3526
- Thursday 8am -- 9am, Phelps 3526 -->

<p>Virtual</p>

<ul>
  <li>Tuesday 4 – 5pm, link in <a href="https://piazza.com/ucsb/fall2024/cs291a">Piazza</a></li>
  <li>Friday 4 – 5pm, link in <a href="https://piazza.com/ucsb/fall2024/cs291a">Piazza</a></li>
</ul>

<h3 id="initial-tasks-due-before">Initial tasks due before</h3>

<p>Monday, September 30 2pm PT</p>

<ul>
  <li>Complete the <a href="https://forms.gle/ypmAEJnCnS4EHgpW6">introduction survey</a></li>
  <li>Join the class on <a href="https://piazza.com/ucsb/fall2024/cs291a">Piazza</a></li>
</ul>

<!-- - Enroll in [AWS Educate](https://www.awseducate.com/Registration?apptype=student&courseview=true) -->

<h3 id="project-0project0-due-before"><a href="/project0/">Project 0</a> due before</h3>

<p>Monday, October 7 2pm PT</p>

<h3 id="project-1project1-due-before"><a href="/project1/">Project 1</a> due before</h3>

<p>Monday, October 14 2pm PT</p>

<h3 id="project-2project2-due-before"><a href="/project2/">Project 2</a> due before</h3>

<p>Monday, October 21 2pm PT</p>

<h3 id="project-3project3-team-message-due-before"><a href="/project3/">Project 3</a> Team Message due before</h3>

<p>Monday, October 21 2pm PT</p>

<h3 id="final-project-team-messageproject-due-before"><a href="/project">Final Project Team Message</a> due before</h3>

<p>Monday, November 4 2pm PT</p>

<h3 id="project-3project3-due-before"><a href="/project3/">Project 3</a> due before</h3>

<p>Monday, November 4 2pm PT</p>

<h3 id="projectprojectproposal-initial-peer-score-message-due-before"><a href="/project/#proposal">Project</a> initial peer score message due before</h3>

<p>Monday, November 27 2pm PT</p>

<h3 id="projectprojectreport-report-draft-for-feedback-due-before"><a href="/project/#report">Project</a> report draft for feedback due before</h3>

<p>Friday, December 6 2pm PT</p>

<h3 id="projectprojectproposal-final-peer-score-message-due-before"><a href="/project/#proposal">Project</a> final peer score message due before</h3>

<p>Friday, December 13 2pm PT</p>

<h3 id="projectprojectreport-report-due-before"><a href="/project/#report">Project</a> report due before</h3>

<p>Friday, December 13 2pm PT</p>

<h3 id="projectprojectvideo-video-due-before"><a href="/project/#video">Project</a> video due before</h3>

<p>Friday, December 13 2pm PT</p>

<h2 id="class-resources">Class Resources</h2>

<p><a href="https://piazza.com/ucsb/fall2024/cs291a">Piazza</a>: Use to receive class announcements, ask and
answer questions, and to communicate with instructor. Access code is available
in Google Drive and will be shared in the first class.</p>

<p><a href="https://github.com/scalableinternetservices">GitHub</a>: Contains content for
this site. Additionally all student projects will live here.</p>

<h2 id="textbooks">Textbooks</h2>

<p><a href="https://www.amazon.com/High-Performance-Browser-Networking-performance/dp/1449344763">High Performance Browser Networking</a><br />
ISBN: 9781449344764<br />
<em><a href="https://hpbn.co/">Available online</a>.</em><br />
Note: The online version is slightly more up-to-date.</p>

<p><a href="https://www.railstutorial.org/book">The Ruby On Rails Tutorial</a><br />
<!-- _[Complete 3rd edition available online](https://3rd-edition.railstutorial.org/book)_   -->
Optional
Note: This book is only useful once we get to the primary project.</p>

</div>

        </div>
        <div class="col-md-9">
          <h1 id="scalable-internet-services-syllabus">Scalable Internet Services Syllabus</h1>

<h2 id="course-description">Course Description</h2>

<p>This course explores advanced topics in highly scalable Internet services and
their underlying systems’ architecture. Software today is primarily delivered
as a service: accessible globally via web browsers and mobile applications, and
backed by millions of servers. Modern web frameworks (e.g., <a href="http://rubyonrails.org/">Ruby on
Rails</a>, <a href="https://www.djangoproject.com">Django</a>, and
<a href="https://expressjs.com">Express</a>), and continuous improvements to cloud
providers (e.g., <a href="https://aws.amazon.com">Amazon Web Services</a>, <a href="https://cloud.google.com">Google Cloud
Platform</a>, and <a href="https://azure.microsoft.com/en-us/">Microsoft
Azure</a>) make it increasingly easier to
build and deploy these systems.</p>

<p>Despite these advances, building scalable Internet services today still
requires an understanding of topics like caching, load balancing, security, and
monitoring. In this course we will examine these topics and more: the state of
the art in building scalable Internet services.</p>

<h2 id="learning-outcomes">Learning Outcomes</h2>

<p>By the end of this course students will be able to:</p>

<ul>
  <li>
    <p>write and deploy highly scalable web functions using <a href="https://aws.amazon.com/lambda/">AWS
Lambda</a></p>
  </li>
  <li>
    <p>write a modern front end client application using
<a href="https://reactjs.org">React</a></p>
  </li>
  <li>
    <p>create a <a href="http://rubyonrails.org/">Ruby on Rails</a> web service and deploy it
via <a href="https://aws.amazon.com/elasticbeanstalk/">AWS Elastic Beanstalk</a></p>
  </li>
  <li>
    <p>measure the performance of various components of a web service</p>
  </li>
  <li>
    <p>discover and resolve bottlenecks in a web service</p>
  </li>
</ul>

<h2 id="class-content-and-interactions">Class Content and Interactions</h2>

<h3 id="synchronous-classes">Synchronous Classes</h3>

<p>All core course topics, covering the essentials of building large scale
Internet services, will be presented via in-person lectures.</p>

<p>Class will meet twice a week during the scheduled class time unless otherwise
mentioned. Students are encouraged to attend in order to ask and answer
questions, and explore the material in more depth.</p>

<h3 id="piazza">Piazza</h3>

<p>All students are expected to join the class on Piazza as class announcements
will be made there. Additionally Piazza is used for offline questions about the
class content and its projects. Students are able to submit anonymously, though
anonymous content will not be counted toward participation. Students are
strongly encouraged to answer each other’s questions by improving upon the
“student answer”.</p>

<p>Please create a new post for each distinct question, rather than asking new
questions as a follow up to an existing post. Follow-ups are useful to obtain
more information necessary to answer a question, or to work through possible
solutions to a question.</p>

<p>All one-on-one offline communication with the instructors for content
pertaining to this class should be conducted via Piazza. Please do not reach
out to the instructor via email for class related communications.</p>

<h3 id="team-check-ins">Team Check-ins</h3>

<p>Once the primary project has started in week 5, teams will meet with
instructors once each week, via Zoom. These meetings will be scheduled for
approximately 15 minutes.</p>

<h2 id="projects">Projects</h2>

<h3 id="initial-projects">Initial Projects</h3>

<p>There will be four projects in the first five weeks of the course, one per week
with the fourth project spanning two weeks. These projects will ensure students
have the basic knowledge to build and deploy modern, simple, and scalable web
services without needing a deep understanding of how the underlying systems
enable scalability. The first three projects are to be completed individually,
and the fourth completed as a pair.</p>

<h3 id="primary-project">Primary Project</h3>

<p>The goal of the course’s primary project is for students to experience and
resolve pain points encountered when building and deploying a moderate-sized
scalable web service. Students will do this using some of the latest web
technologies in order to learn how to tackle scalability and fault-tolerance
concerns. Projects will be conducted in agile teams of four to six students,
and each team will build their own scalable web site using fundamental web
technologies and the <a href="http://rubyonrails.org/">Ruby on Rails</a> framework. A team
may not be comprised of more than two undergraduate or BS/MS students.</p>

<h2 id="grading">Grading</h2>

<table>
  <thead>
    <tr>
      <th style="text-align: left">Percent</th>
      <th style="text-align: right">Item</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td style="text-align: left">3</td>
      <td style="text-align: right"><a href="/project0/">Project 0</a> (Static Web Page)</td>
    </tr>
    <tr>
      <td style="text-align: left">6</td>
      <td style="text-align: right"><a href="/project1/">Project 1</a> (RubyKoans)</td>
    </tr>
    <tr>
      <td style="text-align: left">9</td>
      <td style="text-align: right"><a href="/project2/">Project 2</a> (AWS Lambda)</td>
    </tr>
    <tr>
      <td style="text-align: left">12</td>
      <td style="text-align: right"><a href="/project3/">Project 3</a> (Rails demo app)</td>
    </tr>
    <tr>
      <td style="text-align: left">65</td>
      <td style="text-align: right"><a href="/project/">Primary Project</a> Individual Score</td>
    </tr>
    <tr>
      <td style="text-align: left">5</td>
      <td style="text-align: right">Participation</td>
    </tr>
  </tbody>
</table>

<p class="table table-striped">Participation is an important part of keeping a class engaging. Participation
can be earned by asking or answering questions during synchronous classes, and
asking or answering public questions on Piazza. Note that neither private
conversations with the instructor, nor participation during team check-ins
count toward the participation score.</p>

<p>Projects 0 through 3 are scored as either complete (<code class="language-plaintext highlighter-rouge">100%</code>) or incomplete
(<code class="language-plaintext highlighter-rouge">0%</code>); there is no fractional score other than as described below for late
submissions.</p>

<p>Late submissions incur a <code class="language-plaintext highlighter-rouge">1%</code> penalty for every five-minutes late rounded up.
For example, if the deadline is before <code class="language-plaintext highlighter-rouge">2pm</code>, an assignment submitted at
<code class="language-plaintext highlighter-rouge">14:00:00</code> (5 minutes late) will receive <code class="language-plaintext highlighter-rouge">99%</code> of its score, and an assignment
submitted at <code class="language-plaintext highlighter-rouge">15:00:00</code> (65 minutes late) will receive only <code class="language-plaintext highlighter-rouge">87%</code> of its score.</p>

<h3 id="primary-project-score">Primary Project Score</h3>

<p>A project’s score is primarily based on the team’s description of their
iterative approach to load testing and scaling their web service as described
in their project report and highlighted in their project video. Objectively
these components break down into:</p>

<table>
  <thead>
    <tr>
      <th style="text-align: left">Percent</th>
      <th style="text-align: right">Item</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td style="text-align: left">50</td>
      <td style="text-align: right">iterative approach to load testing and scaling</td>
    </tr>
    <tr>
      <td style="text-align: left">20</td>
      <td style="text-align: right">web service complexity</td>
    </tr>
    <tr>
      <td style="text-align: left">15</td>
      <td style="text-align: right">quality of project report</td>
    </tr>
    <tr>
      <td style="text-align: left">15</td>
      <td style="text-align: right">quality of project video</td>
    </tr>
  </tbody>
</table>

<h3 class="table table-striped" id="primary-project-individual-score">Primary Project Individual Score</h3>

<p>The individual score is computed by multiplying the project score by the
student’s peer score. Peer scores are computed by summing the relative percent
of <em>work</em> each individual’s teammates confidentially assigns them.</p>

<p>For example, a three person team may assign the following peer scores:</p>

<table>
  <thead>
    <tr>
      <th style="text-align: center"> </th>
      <th style="text-align: center">Alice</th>
      <th style="text-align: center">Bob</th>
      <th style="text-align: center">Chuck</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td style="text-align: center">Alice</td>
      <td style="text-align: center">-</td>
      <td style="text-align: center">55%</td>
      <td style="text-align: center">45%</td>
    </tr>
    <tr>
      <td style="text-align: center">Bob</td>
      <td style="text-align: center">60%</td>
      <td style="text-align: center">-</td>
      <td style="text-align: center">40%</td>
    </tr>
    <tr>
      <td style="text-align: center">Chuck</td>
      <td style="text-align: center">52%</td>
      <td style="text-align: center">48%</td>
      <td style="text-align: center">-</td>
    </tr>
  </tbody>
  <tfoot>
    <tr>
      <td style="text-align: center"><strong>Total</strong></td>
      <td style="text-align: center"><strong>112%</strong></td>
      <td style="text-align: center"><strong>103%</strong></td>
      <td style="text-align: center"><strong>85%</strong></td>
    </tr>
  </tfoot>
</table>

<p class="table table-striped">The observations from the data in the table above are:</p>

<ul>
  <li>Alice reported Bob (<code class="language-plaintext highlighter-rouge">55%</code>) as having contributed more work than Chuck
(<code class="language-plaintext highlighter-rouge">45%</code>).</li>
  <li>Similarly, Bob reported that Alice (<code class="language-plaintext highlighter-rouge">60%</code>) contributed more work than Chuck
(<code class="language-plaintext highlighter-rouge">40%</code>).</li>
  <li>Finally, Chuck reported that Alice (<code class="language-plaintext highlighter-rouge">52%</code>) contributed slightly more work
than Bob (<code class="language-plaintext highlighter-rouge">48%</code>).</li>
</ul>

<p>With these values, Alice’s peer score would be <code class="language-plaintext highlighter-rouge">112%</code>, Bob’s <code class="language-plaintext highlighter-rouge">103%</code>, and
Chuck’s <code class="language-plaintext highlighter-rouge">85%</code>. With a project score of <code class="language-plaintext highlighter-rouge">95%</code>, Alice’s Primary Project
Individual Score would be <code class="language-plaintext highlighter-rouge">106.4%</code>, Bob’s <code class="language-plaintext highlighter-rouge">97.85%</code>, and Chuck’s <code class="language-plaintext highlighter-rouge">80.75%</code>.</p>

<p>We will confidentially conduct the peer score process once during the course:</p>

<ul>
  <li>Monday, November 18</li>
</ul>

<p>The first peer score is intended to help students see if they need to
make any adjustments to their team contributions. Only the outcome of the final
peer score will be used to compute an individual’s score. Any moderate
deviations of more than two points from equal contribution will require
justification, and may be followed up on by the instructor.</p>

<h3 id="letter-grades">Letter Grades</h3>

<p>Letter grades will be assigned as follows:</p>

<table>
  <thead>
    <tr>
      <th style="text-align: center">Percent</th>
      <th style="text-align: left">Grade</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td style="text-align: center">96 ⅔</td>
      <td style="text-align: left">A+</td>
    </tr>
    <tr>
      <td style="text-align: center">93 ⅓</td>
      <td style="text-align: left">A</td>
    </tr>
    <tr>
      <td style="text-align: center">90</td>
      <td style="text-align: left">A-</td>
    </tr>
    <tr>
      <td style="text-align: center">86 ⅔</td>
      <td style="text-align: left">B+</td>
    </tr>
    <tr>
      <td style="text-align: center">83 ⅓</td>
      <td style="text-align: left">B</td>
    </tr>
    <tr>
      <td style="text-align: center">80</td>
      <td style="text-align: left">B-</td>
    </tr>
    <tr>
      <td style="text-align: center">76 ⅔</td>
      <td style="text-align: left">C+</td>
    </tr>
    <tr>
      <td style="text-align: center">73 ⅓</td>
      <td style="text-align: left">C</td>
    </tr>
    <tr>
      <td style="text-align: center">0</td>
      <td style="text-align: left">F</td>
    </tr>
  </tbody>
</table>

<p class="table table-striped">The number listed is the lower bound of the percent grade for the given
range. It is expected that each person is a relatively equal contributor on
their team, with the exception that there may be significant positive
outliers. Additionally, it is expected that each team does a solid job on their
project. As a result, please note the drop to an <code class="language-plaintext highlighter-rouge">F</code> grade immediately
following the <code class="language-plaintext highlighter-rouge">C</code> range.</p>

        </div>
      </div>
    </div>

    <div class="container-fluid">
  <div class="row-fluid">
    <div class="span12 footer navbar-inverse navbar-fixed-bottom">
      <p class="copyright">
        &copy; 2014-2021 <a href="https://www.linkedin.com/in/bryceboe/">Dr. Bryce Boe</a>
        &copy; 2022 <a href="https://www.linkedin.com/in/nevenagolubovic/">Dr. Nevena Golubovic</a>
        &copy; 2023 <a href="https://www.linkedin.com/in/shyr-shea-chang-6426271b8/">Dr. Shyr-Shea Chang</a>
        &copy; 2024 <a href="https://www.linkedin.com/in/zachary-walker-6a219059/">Zach Walker</a>.
      </p>
    </div>
  </div>
</div>


  <script src="https://code.jquery.com/jquery-2.1.4.min.js"></script>
  <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js"></script>

  </body>

</html>

Whois info of domain

Domain Name: CS291.COM
Registry Domain ID: 2054049567_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrar.amazon.com
Registrar URL: http://registrar.amazon.com
Updated Date: 2024-07-17T21:57:16Z
Creation Date: 2016-08-20T19:19:41Z
Registry Expiry Date: 2025-08-20T19:19:41Z
Registrar: Amazon Registrar, Inc.
Registrar IANA ID: 468
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.2024422253
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS-134.AWSDNS-16.COM
Name Server: NS-1440.AWSDNS-52.ORG
Name Server: NS-1978.AWSDNS-55.CO.UK
Name Server: NS-957.AWSDNS-55.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2025-04-30T17:01:27Z <<<
For more information on Whois status codes, please visit https://icann.org/epp
NOTICE: The expiration date displayed in this record is the date the
TERMS OF USE: You are not authorized to access or query our Whois
by the following terms of use: You agree that you may use this Data only
to: (1) allow, enable, or otherwise support the transmission of mass