{"id":3849,"date":"2026-11-14T15:03:31","date_gmt":"2026-11-14T12:03:31","guid":{"rendered":"https:\/\/niteducation.com\/resources\/?p=3849"},"modified":"2026-11-16T11:45:23","modified_gmt":"2026-11-16T08:45:23","slug":"what-happens-when-you-type-a-url","status":"publish","type":"post","link":"https:\/\/niteducation.com\/resources\/what-happens-when-you-type-a-url\/","title":{"rendered":"What Happens When You Type a URL Into Your Browser?"},"content":{"rendered":"\n<!--\n  Newton Institute of Technology \u2014 Article 254\n  Locked Master Stylesheet v6.3 Premium. NIT Visual Style Benchmark 1 split-hero treatment.\n  WordPress supplies the only semantic H1; the article hero uses .nit-hero__title.\n  Paste the following unminified fragment into the WordPress article body.\n  The locked v6.3 stylesheet is loaded site-wide; do not paste CSS into this production body.\n  No article-specific CSS, inline styles, scripts, Base64 images, or generic code windows.\n  Intended slug: what-happens-when-you-type-a-url\n-->\n<article class=\"nit-article nit-article--pathway-guide nit-article--c-plus-degree nit-article--software\" aria-labelledby=\"nit-article-title\" itemscope=\"\" itemtype=\"https:\/\/schema.org\/Article\">\n  <meta itemprop=\"inLanguage\" content=\"en-KE\">\n  <meta itemprop=\"author\" content=\"Newton Institute of Technology Editorial Team\">\n\n  <div class=\"nit-pg-hero\" aria-labelledby=\"nit-article-title\">\n    <div>\n      <p class=\"nit-pg-kicker\">ICT Foundations <\/p>\n      <p class=\"nit-hero__title\" id=\"nit-article-title\" itemprop=\"headline\">What Happens When You Type a Website Address Into Your Browser?<\/p>\n      <p class=\"nit-pg-hero__line\">DNS <i>\u2192<\/i> HTTPS <i>\u2192<\/i> web servers <i>\u2192<\/i> your screen<\/p>\n      <p class=\"nit-pg-hero__summary\" itemprop=\"description\">Follow a URL from the address bar to a visible webpage. Understand every major stage, then investigate real website requests using Chrome DevTools.<\/p>\n      <div class=\"nit-pg-hero__actions\">\n        <a class=\"nit-pg-button nit-pg-button--gold\" href=\"#quick-answer\">See the six steps<\/a>\n        <a class=\"nit-pg-button nit-pg-button--outline\" href=\"#practical-lab\">Try the browser lab<\/a>\n      <\/div>\n    <\/div>\n    <div class=\"nit-deg-hero__art\" aria-label=\"A URL at the centre of the DNS, HTTPS, HTTP and browser-rendering process\">\n      <p>From address bar to webpage<\/p>\n      <div class=\"nit-deg-orbit\" aria-hidden=\"true\">\n        <strong>W<\/strong>\n        <span class=\"nit-deg-orbit__chip nit-deg-orbit__chip--tech\">DNS<\/span>\n        <span class=\"nit-deg-orbit__chip nit-deg-orbit__chip--health\">TLS<\/span>\n        <span class=\"nit-deg-orbit__chip nit-deg-orbit__chip--business\">HTTP<\/span>\n        <span class=\"nit-deg-orbit__chip nit-deg-orbit__chip--stem\">PAGE<\/span>\n      <\/div>\n      <div class=\"nit-deg-hero__note\">\n        <span>Beginner learning path<\/span>\n        <strong>Locate \u00b7 Connect \u00b7 Request \u00b7 Render<\/strong>\n        <small>Learn the process, then inspect what your browser actually did.<\/small>\n      <\/div>\n    <\/div>\n    <div class=\"nit-pg-hero__meta\" aria-label=\"Article metadata\">\n      <p><span>Prepared by<\/span>NIT Editorial Team<\/p>\n      <p><span>Subject<\/span>How websites load<\/p>\n      <p><span>Learn by doing<\/span>Chrome Network lab<\/p>\n      <p><span>Reviewed<\/span>13 Nov 2026<\/p>\n    <\/div>\n  <\/div>\n\n  <div class=\"nit-article__body\" itemprop=\"articleBody\">\n\n    <section class=\"nit-quick-answer\" id=\"quick-answer\" aria-labelledby=\"quick-answer-heading\">\n      <div class=\"nit-quick-answer__head\">\n        <span class=\"nit-quick-answer__mark\" aria-hidden=\"true\">6<\/span>\n        <div>\n          <p class=\"nit-quick-answer__label\">Direct answer<\/p>\n          <p class=\"nit-quick-answer__kicker\" id=\"quick-answer-heading\">What happens after you press Enter?<\/p>\n        <\/div>\n      <\/div>\n      <div class=\"nit-quick-answer__body\">\n        <p class=\"nit-quick-answer__text\"><strong>Your browser interprets the URL, finds the destination using DNS if necessary, opens or reuses a network connection, protects HTTPS communication with TLS, exchanges HTTP requests and responses, and renders the resources into a webpage.<\/strong> Those stages can overlap or be skipped when cached information and existing connections are available. <a href=\"#source-1\">[1]<\/a> <a href=\"#source-8\">[8]<\/a><\/p>\n        <ul class=\"nit-quick-answer__signals\" aria-label=\"Six parts of a website visit\">\n          <li>URL: which resource?<\/li>\n          <li>DNS: where to connect?<\/li>\n          <li>Network: communicate<\/li>\n          <li>TLS: protect HTTPS<\/li>\n          <li>HTTP: request and respond<\/li>\n        <\/ul>\n      <\/div>\n    <\/section>\n\n    <nav class=\"nit-pg-nav\" aria-label=\"Contents\">\n      <p>Explore the journey<\/p>\n      <div>\n        <a href=\"#six-stages\">Six stages<\/a>\n        <a href=\"#url\">The URL<\/a>\n        <a href=\"#dns\">DNS explained<\/a>\n        <a href=\"#connection\">Connections<\/a>\n        <a href=\"#https\">HTTPS<\/a>\n        <a href=\"#http\">Web servers<\/a>\n        <a href=\"#rendering\">Rendering<\/a>\n        <a href=\"#practical-lab\">Browser lab<\/a>\n        <a href=\"#troubleshooting\">Troubleshooting<\/a>\n        <a href=\"#faq\">Questions<\/a>\n      <\/div>\n    <\/nav>\n\n    <section class=\"nit-pg-section\" id=\"six-stages\" aria-labelledby=\"six-stages-heading\">\n          <p class=\"nit-pg-eyebrow\">Start with the big picture<\/p>\n          <h2 id=\"six-stages-heading\">Six stages between a URL and a webpage<\/h2>\n            <p>You open Chrome on your phone, enter <strong>https:\/\/niteducation.com\/<\/strong> and press Enter. It looks like one action. Underneath, different technologies perform different jobs.<\/p>\n        <div class=\"nit-curriculum-grid\">\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">01 \u00b7 URL<\/span>\n            <h3>Interpret the address<\/h3>\n            <p>The browser identifies the website, scheme and requested path.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">02 \u00b7 DNS<\/span>\n            <h3>Locate the destination<\/h3>\n            <p>A resolver supplies network information, such as an IP address, if a lookup is needed.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">03 \u00b7 Network<\/span>\n            <h3>Connect<\/h3>\n            <p>The browser establishes or reuses a suitable TCP or QUIC connection.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">04 \u00b7 TLS<\/span>\n            <h3>Secure HTTPS<\/h3>\n            <p>TLS authenticates the relevant secure endpoint and protects communication.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">05 \u00b7 HTTP<\/span>\n            <h3>Request content<\/h3>\n            <p>A web service handles the request and returns a response or a redirect.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">06 \u00b7 Browser<\/span>\n            <h3>Display the page<\/h3>\n            <p>HTML, CSS, JavaScript and other resources are processed into the visible interface.<\/p>\n          <\/article>\n        <\/div>\n      <p>These are responsibilities, not six mandatory fresh operations on every visit. A cached response or reusable connection can change what happens. <a href=\"#source-1\" aria-label=\"Reference 1\">[1]<\/a> <a href=\"#source-4\" aria-label=\"Reference 4\">[4]<\/a><\/p>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"url\" aria-labelledby=\"url-heading\">\n          <p class=\"nit-pg-eyebrow\">Stage 01 \u00b7 Understand the destination<\/p>\n          <h2 id=\"url-heading\">What is a website address or URL?<\/h2>\n            <p>A <strong>URL (Uniform Resource Locator)<\/strong> identifies a resource and how to access it. Consider <strong>https:\/\/niteducation.com\/resources\/<\/strong>.<\/p>\n        <div class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\" aria-label=\"Part of the URL comparison table\">\n          <table class=\"nit-pg-table\">\n            <thead>\n              <tr>\n                <th scope=\"col\">Part of the URL<\/th>\n                <th scope=\"col\">Example<\/th>\n                <th scope=\"col\">Purpose<\/th>\n              <\/tr>\n            <\/thead>\n            <tbody>\n              <tr>\n                <td>Scheme<\/td>\n                <td>https:\/\/<\/td>\n                <td>Indicates HTTPS access.<\/td>\n              <\/tr>\n              <tr>\n                <td>Hostname<\/td>\n                <td>niteducation.com<\/td>\n                <td>Identifies the requested website.<\/td>\n              <\/tr>\n              <tr>\n                <td>Path<\/td>\n                <td>\/resources\/<\/td>\n                <td>Identifies a resource or location within the website.<\/td>\n              <\/tr>\n            <\/tbody>\n          <\/table>\n        <\/div>\n        <p class=\"nit-pg-table-note\">On narrow screens, swipe horizontally across the table. A URL can also include a query string beginning with ? and a fragment beginning with #. The fragment is handled by the browser rather than sent as the HTTP request target.<\/p>\n      <h3>Is the domain the same as the full URL?<\/h3>\n      <p>No. <strong>niteducation.com<\/strong> is a domain name. A full URL also indicates how the resource should be accessed and which page or resource is requested.<\/p>\n      <h3>What if you type only the domain name?<\/h3>\n      <p>Modern browsers commonly attempt HTTPS if you enter a domain without its scheme. They may also interpret ordinary words in the address bar as a search query. Before requesting a page, the browser checks whether cached information or an existing connection is available.<\/p>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"dns\" aria-labelledby=\"dns-heading\">\n          <p class=\"nit-pg-eyebrow\">Stage 02 \u00b7 Find a destination<\/p>\n          <h2 id=\"dns-heading\">How does DNS find a website?<\/h2>\n            <p>People remember names such as <strong>niteducation.com<\/strong>. Networks use IP addresses to route packets. The <strong>Domain Name System (DNS)<\/strong> helps translate hostnames into useful records, including IPv4 and IPv6 addresses. <a href=\"#source-2\" aria-label=\"Reference 2\">[2]<\/a><\/p>\n      <h3>What is an IP address?<\/h3>\n      <p>An IP address is a numerical network address. For illustration, an IPv4 address might look like <strong>192.0.2.25<\/strong> and an IPv6 address like <strong>2001:db8::25<\/strong>. These are reserved documentation examples\u2014not verified NIT addresses.<\/p>\n      <p>A hostname can have several addresses. A DNS answer may direct a visitor to a CDN or load balancer rather than to the website&#8217;s original hosting computer.<\/p>\n        <div class=\"nit-curriculum-grid\">\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">DNS 01<\/span>\n            <h3>Check saved information<\/h3>\n            <p>The browser or operating system may already have a usable DNS result.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">DNS 02<\/span>\n            <h3>Ask a resolver<\/h3>\n            <p>If needed, the device queries its configured DNS resolver.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">DNS 03<\/span>\n            <h3>Find the record<\/h3>\n            <p>The resolver answers from cache or consults the DNS hierarchy and authoritative servers.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">DNS 04<\/span>\n            <h3>Continue navigation<\/h3>\n            <p>The browser uses the returned information to communicate with a suitable destination.<\/p>\n          <\/article>\n        <\/div>\n      <h3>Does DNS send the webpage itself?<\/h3>\n      <p>No. DNS helps answer <strong>where to reach a destination<\/strong>. The HTML, images, scripts and stylesheets are obtained separately through web requests.<\/p>\n      <div class=\"nit-callout nit-callout--info\">\n            <p class=\"nit-callout__title\">A useful analogy<\/p>\n            <p>Finding a teacher\u2019s office by their name is like resolving a domain name. Reception helps you find a location; reception does not hand you every document kept in that office. Likewise, DNS is not the server that delivers the whole page.<\/p>\n          <\/div>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"connection\" aria-labelledby=\"connection-heading\">\n          <p class=\"nit-pg-eyebrow\">Stage 03 \u00b7 Move data<\/p>\n          <h2 id=\"connection-heading\">How does your device connect to the website?<\/h2>\n            <p>On Wi-Fi, your device ordinarily communicates through a local network and an internet connection. On mobile data, it communicates through the mobile network. Routers forward packets across interconnected networks towards the destination.<\/p>\n      <h3>What is TCP?<\/h3>\n      <p><strong>TCP<\/strong> provides reliable, ordered data delivery between applications. A new TCP connection normally begins with a three-way handshake, often summarised as <strong>SYN \u2192 SYN-ACK \u2192 ACK<\/strong>.<\/p>\n      <h3>Does every HTTPS website use TCP?<\/h3>\n      <p>No. HTTP\/1.1 and HTTP\/2 typically use TCP, while <strong>HTTP\/3 uses QUIC over UDP<\/strong>. Browsers may also reuse connections instead of establishing a new connection for every resource. <a href=\"#source-4\" aria-label=\"Reference 4\">[4]<\/a><\/p>\n      <h3>Can multiple websites share an IP address?<\/h3>\n      <p>Yes. Multiple website hostnames can share the same address. The requested hostname matters during secure connection establishment and web-service request processing.<\/p>\n      <div class=\"nit-callout nit-callout--info\">\n            <p class=\"nit-callout__title\">What \u201cthe server\u201d really means<\/p>\n            <p>A browser might communicate with a CDN, reverse proxy or load balancer first. The website can involve several services even though you see one URL.<\/p>\n          <\/div>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"https\" aria-labelledby=\"https-heading\">\n          <p class=\"nit-pg-eyebrow\">Stage 04 \u00b7 Protect the visit<\/p>\n          <h2 id=\"https-heading\">What happens when the browser uses HTTPS?<\/h2>\n            <p><strong>HTTPS<\/strong> is HTTP protected using <strong>Transport Layer Security (TLS)<\/strong>. TLS helps secure communication with the HTTPS endpoint. <a href=\"#source-5\" aria-label=\"Reference 5\">[5]<\/a><\/p>\n        <div class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\" aria-label=\"Protection comparison table\">\n          <table class=\"nit-pg-table\">\n            <thead>\n              <tr>\n                <th scope=\"col\">Protection<\/th>\n                <th scope=\"col\">What it helps achieve<\/th>\n              <\/tr>\n            <\/thead>\n            <tbody>\n              <tr>\n                <th scope=\"row\">Encryption<\/th>\n                <td>Prevents unauthorised observers on the network path from readily reading protected communication.<\/td>\n              <\/tr>\n              <tr>\n                <th scope=\"row\">Integrity<\/th>\n                <td>Helps detect unauthorised changes in protected messages.<\/td>\n              <\/tr>\n              <tr>\n                <th scope=\"row\">Authentication<\/th>\n                <td>Helps the browser verify that the endpoint is authorised to represent the requested hostname.<\/td>\n              <\/tr>\n            <\/tbody>\n          <\/table>\n        <\/div>\n        <p class=\"nit-pg-table-note\">On narrow screens, swipe horizontally to read every column.<\/p>\n      <p>During a new secure connection, certificate verification and TLS negotiation establish the relevant protection. HTTP\/3 integrates TLS with the QUIC connection procedure, so not every secure session follows the same underlying transport sequence.<\/p>\n      <h3>Does HTTPS mean the website is honest?<\/h3>\n      <p><strong>No.<\/strong> HTTPS protects communication; it does not guarantee that the website operator is trustworthy. A misleading or fraudulent domain can still have a valid certificate. Always check the exact hostname before entering passwords or payment information, and do not bypass a certificate warning just to open a page.<\/p>\n      <h3>Does HTTPS hide all browsing information?<\/h3>\n      <p>No. Depending on DNS and network configuration, observers may still learn information about the destination. HTTPS is essential protection, not complete anonymity.<\/p>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"http\" aria-labelledby=\"http-heading\">\n          <p class=\"nit-pg-eyebrow\">Stage 05 \u00b7 Request the resource<\/p>\n          <h2 id=\"http-heading\">What does the browser ask a web server to do?<\/h2>\n            <p>HTTP defines how a client such as a browser and a web service exchange requests and responses. When you navigate to <strong>https:\/\/niteducation.com\/resources\/<\/strong>, the browser may make a <strong>GET<\/strong> request for the path <strong>\/resources\/<\/strong>. Actual request representation depends on the HTTP version. <a href=\"#source-3\" aria-label=\"Reference 3\">[3]<\/a><\/p>\n      <h3>What happens on the server?<\/h3>\n      <p>The server may return an existing HTML document, generate content using application code, retrieve permitted database information, or use cached material. Not every request needs a database or a separate API call.<\/p>\n      <h3>What does the HTTP status mean?<\/h3>\n        <div class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\" aria-label=\"Response comparison table\">\n          <table class=\"nit-pg-table\">\n            <thead>\n              <tr>\n                <th scope=\"col\">Response<\/th>\n                <th scope=\"col\">What it generally means<\/th>\n              <\/tr>\n            <\/thead>\n            <tbody>\n              <tr>\n                <td>200 OK<\/td>\n                <td>The HTTP request succeeded.<\/td>\n              <\/tr>\n              <tr>\n                <td>301 Moved Permanently<\/td>\n                <td>The resource has a new permanent address.<\/td>\n              <\/tr>\n              <tr>\n                <td>302 Found<\/td>\n                <td>A temporary redirect is indicated.<\/td>\n              <\/tr>\n              <tr>\n                <td>304 Not Modified<\/td>\n                <td>A cached representation can be reused after validation.<\/td>\n              <\/tr>\n              <tr>\n                <td>403 Forbidden<\/td>\n                <td>The server refuses to fulfil the request.<\/td>\n              <\/tr>\n              <tr>\n                <td>404 Not Found<\/td>\n                <td>The requested resource was not found.<\/td>\n              <\/tr>\n              <tr>\n                <td>500 Internal Server Error<\/td>\n                <td>The server encountered a problem.<\/td>\n              <\/tr>\n              <tr>\n                <td>502 Bad Gateway<\/td>\n                <td>A gateway received an invalid upstream response.<\/td>\n              <\/tr>\n            <\/tbody>\n          <\/table>\n        <\/div>\n        <p class=\"nit-pg-table-note\">On narrow screens, swipe horizontally across the table. A redirect is not necessarily an error. A successful 200 response also does not prove that every image, script or interactive feature works.<\/p>\n      <h3>Does an HTTP 200 response prove the entire site works?<\/h3>\n      <p>No. The main document might return 200 while a stylesheet returns 404 or a button fails because of a JavaScript error. Document delivery, resource loading and application behaviour must be checked separately.<\/p>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"rendering\" aria-labelledby=\"rendering-heading\">\n          <p class=\"nit-pg-eyebrow\">Stage 06 \u00b7 Build the screen<\/p>\n          <h2 id=\"rendering-heading\">How does a browser turn files into a webpage?<\/h2>\n            <p>The browser interprets the HTML document and other resources to build the visible interface. This is called <strong>rendering<\/strong>. <a href=\"#source-8\" aria-label=\"Reference 8\">[8]<\/a><\/p>\n        <div class=\"nit-curriculum-grid\">\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">Structure<\/span>\n            <h3>HTML<\/h3>\n            <p>Describes headings, paragraphs, links, tables, forms and other document content.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">Appearance<\/span>\n            <h3>CSS<\/h3>\n            <p>Controls typography, colours, spacing, layouts and responsive presentation.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">Behaviour<\/span>\n            <h3>JavaScript<\/h3>\n            <p>Can handle interactions, change the document and request additional information.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">Rendering<\/span>\n            <h3>DOM + layout + paint<\/h3>\n            <p>The browser parses document structure, applies styling, calculates layout and paints visible elements.<\/p>\n          <\/article>\n        <\/div>\n      <p>Rendering and resource loading can overlap. A heading may appear before a large image finishes downloading. Some pages can display useful content without JavaScript; others require it for important interactions.<\/p>\n      <div class=\"nit-callout nit-callout--info\">\n            <p class=\"nit-callout__title\">A visible page is not always a complete page<\/p>\n            <p>A successful HTML request does not guarantee that CSS, images, scripts or forms have worked correctly. The browser may display content while other requests fail.<\/p>\n          <\/div>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"journey\" aria-labelledby=\"journey-heading\">\n          <p class=\"nit-pg-eyebrow\">Put the pieces together<\/p>\n          <h2 id=\"journey-heading\">Follow one NIT website visit from start to finish<\/h2>\n            <p>Amina enters <strong>https:\/\/niteducation.com\/resources\/<\/strong> in her laptop browser. The browser interprets the URL and uses existing destination information or a DNS lookup. It opens or reuses a connection, applies HTTPS protection, and requests the resource.<\/p>\n      <p>A server-side service returns a response, which might include HTML or an instruction to follow another address. The browser processes HTML, CSS, JavaScript and other resources. Once enough information is available, it displays the page. Additional downloads or scripts may continue afterwards.<\/p>\n      <div class=\"nit-callout nit-callout--info\">\n            <p class=\"nit-callout__title\">Four useful diagnostic questions<\/p>\n            <p><strong>Where?<\/strong> DNS and destination information. <strong>How?<\/strong> Networking and secure transport. <strong>What came back?<\/strong> HTTP requests and responses. <strong>Did it work?<\/strong> Resource loading, rendering and interaction.<\/p>\n          <\/div>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"caching\" aria-labelledby=\"caching-heading\">\n          <p class=\"nit-pg-eyebrow\">When you revisit a website<\/p>\n          <h2 id=\"caching-heading\">Why can the second visit behave differently?<\/h2>\n            <p>Browsers can reuse previously downloaded images, stylesheets and other resources subject to their cache rules. DNS results and network connections may also be reused.<\/p>\n      <p>When a cached HTTP response needs checking, the server may return <strong>304 Not Modified<\/strong> to indicate that the saved representation can still be used. This is a normal cache-validation response, not a failed page. <a href=\"#source-6\" aria-label=\"Reference 6\">[6]<\/a><\/p>\n      <p>A repeated visit is not guaranteed to be faster. Website changes, network conditions, browser work and caching rules all matter.<\/p>\n      <div class=\"nit-callout nit-callout--info\">\n            <p class=\"nit-callout__title\">Avoid a common misconception<\/p>\n            <p>Refreshing a webpage does not necessarily repeat DNS resolution, a new TCP connection and a new TLS handshake. Caching and connection reuse change the observed sequence.<\/p>\n          <\/div>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"practical-lab\" aria-labelledby=\"practical-lab-heading\">\n          <p class=\"nit-pg-eyebrow\">Hands-on \u00b7 Chrome DevTools<\/p>\n          <h2 id=\"practical-lab-heading\">Practical lab: investigate a real page load<\/h2>\n            <p>Use <strong>Chrome on a laptop or desktop<\/strong> and an informational webpage such as <strong>https:\/\/niteducation.com\/<\/strong>. The Network panel lets you inspect HTTP requests, responses, initiators, timing and caching evidence. <a href=\"#source-7\" aria-label=\"Reference 7\">[7]<\/a><\/p>\n        <div class=\"nit-curriculum-grid\">\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">LAB 01<\/span>\n            <h3>Open the Network panel<\/h3>\n            <p>Open Chrome, visit the webpage, press Ctrl + Shift + I (Windows\/Linux) or Command + Option + I (Mac), and select Network.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">LAB 02<\/span>\n            <h3>Capture the requests<\/h3>\n            <p>Make sure recording is enabled. Reload the webpage with Network open. Use Preserve log if you want to keep redirect requests.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">LAB 03<\/span>\n            <h3>Inspect the document<\/h3>\n            <p>Select the main Doc request. In Headers, record the Request URL, method, status code and any relevant content type.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">LAB 04<\/span>\n            <h3>Inspect resources<\/h3>\n            <p>Use CSS, JS and Img filters, where available. Find one stylesheet or image and inspect its URL, status and Initiator information.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">LAB 05<\/span>\n            <h3>Check protocol and timing<\/h3>\n            <p>Enable the Protocol column where available. The protocol may show http\/1.1, h2 or h3. Inspect a request\u2019s Timing tab.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">LAB 06<\/span>\n            <h3>Compare caching<\/h3>\n            <p>Reload normally, then enable Disable cache in the Network panel and reload again. Compare transfer sizes and cache indicators.<\/p>\n          <\/article>\n        <\/div>\n      <h3>Optional experiment: slow and offline conditions<\/h3>\n      <p>Use the Network panel&#8217;s throttling controls to simulate a slower network and watch when text, images and other resources appear. An offline simulation may stop fresh requests, although an app with suitable saved content or service-worker behaviour can respond differently. Restore normal network settings after testing.<\/p>\n      <h3>Record your evidence<\/h3>\n        <div class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\" aria-label=\"Observation comparison table\">\n          <table class=\"nit-pg-table\">\n            <thead>\n              <tr>\n                <th scope=\"col\">Observation<\/th>\n                <th scope=\"col\">Your result<\/th>\n                <th scope=\"col\">What the observation can tell you<\/th>\n              <\/tr>\n            <\/thead>\n            <tbody>\n              <tr>\n                <td>Main document URL<\/td>\n                <td>________<\/td>\n                <td>Which resource was requested.<\/td>\n              <\/tr>\n              <tr>\n                <td>Main response status<\/td>\n                <td>________<\/td>\n                <td>How the HTTP request was answered.<\/td>\n              <\/tr>\n              <tr>\n                <td>Protocol, if reported<\/td>\n                <td>________<\/td>\n                <td>Which HTTP protocol the browser used.<\/td>\n              <\/tr>\n              <tr>\n                <td>One CSS or image request<\/td>\n                <td>________<\/td>\n                <td>How one page can involve several requests.<\/td>\n              <\/tr>\n              <tr>\n                <td>Request initiator, if available<\/td>\n                <td>________<\/td>\n                <td>What caused that request.<\/td>\n              <\/tr>\n              <tr>\n                <td>Cache comparison<\/td>\n                <td>________<\/td>\n                <td>Whether browser cache use changed the observed transfers.<\/td>\n              <\/tr>\n              <tr>\n                <td>Timing detail<\/td>\n                <td>________<\/td>\n                <td>A reported phase in the request lifetime.<\/td>\n              <\/tr>\n              <tr>\n                <td>One unproven assumption<\/td>\n                <td>________<\/td>\n                <td>A claim the Network panel alone cannot establish.<\/td>\n              <\/tr>\n            <\/tbody>\n          <\/table>\n        <\/div>\n        <p class=\"nit-pg-table-note\">On narrow screens, swipe horizontally across the table. Only record values you actually observe. Request logs can include cookies, tokens and sensitive URLs; do not share them unredacted.<\/p>\n      <h3>What can this exercise actually prove?<\/h3>\n      <p>It lets you observe requests, response codes, caching indicators and available timing. It does <strong>not<\/strong> show the entire DNS hierarchy, every router along the path, or all underlying TLS messages. A missing timing phase can reflect connection reuse or tool limitations rather than an absence of networking.<\/p>\n      <h3>What if you only have a phone?<\/h3>\n      <p>You can still inspect the URL and HTTPS scheme and observe how content appears. The standard desktop Chrome DevTools Network panel is not directly available as an ordinary built-in panel in Chrome for Android. A desktop computer or configured remote debugging setup is best for this lab.<\/p>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"troubleshooting\" aria-labelledby=\"troubleshooting-heading\">\n          <p class=\"nit-pg-eyebrow\">Apply what you learned<\/p>\n          <h2 id=\"troubleshooting-heading\">When a website fails: investigate the right stage<\/h2>\n            <p>Instead of assuming every loading problem is caused by the internet connection, ask which stage produced the first useful evidence.<\/p>\n        <div class=\"nit-pg-table-wrap\" role=\"region\" tabindex=\"0\" aria-label=\"Symptom comparison table\">\n          <table class=\"nit-pg-table\">\n            <thead>\n              <tr>\n                <th scope=\"col\">Symptom<\/th>\n                <th scope=\"col\">Likely area to investigate<\/th>\n                <th scope=\"col\">Useful first check<\/th>\n              <\/tr>\n            <\/thead>\n            <tbody>\n              <tr>\n                <td>No websites load<\/td>\n                <td>Device or internet connection<\/td>\n                <td>Verify Wi-Fi\/mobile data and whether any other page opens.<\/td>\n              <\/tr>\n              <tr>\n                <td>The hostname cannot be resolved<\/td>\n                <td>Domain name or DNS<\/td>\n                <td>Recheck the spelling and any DNS error.<\/td>\n              <\/tr>\n              <tr>\n                <td>The connection times out<\/td>\n                <td>Network path or destination service<\/td>\n                <td>Try another site and check whether the service is responding.<\/td>\n              <\/tr>\n              <tr>\n                <td>Certificate warning<\/td>\n                <td>TLS certificate or validation<\/td>\n                <td>Verify domain and device clock; do not bypass the warning.<\/td>\n              <\/tr>\n              <tr>\n                <td>404 Not Found<\/td>\n                <td>Requested resource\/path<\/td>\n                <td>Check the path or navigate from the homepage.<\/td>\n              <\/tr>\n              <tr>\n                <td>500 or 502<\/td>\n                <td>Server or upstream service<\/td>\n                <td>Retry later or report the exact response.<\/td>\n              <\/tr>\n              <tr>\n                <td>Text appears without styling<\/td>\n                <td>CSS resource or stylesheet application<\/td>\n                <td>Inspect CSS requests and associated errors.<\/td>\n              <\/tr>\n              <tr>\n                <td>Images missing<\/td>\n                <td>Individual image resources<\/td>\n                <td>Inspect image URLs and request statuses.<\/td>\n              <\/tr>\n              <tr>\n                <td>Button does nothing<\/td>\n                <td>JavaScript or application logic<\/td>\n                <td>Inspect the Console and requests triggered by the action.<\/td>\n              <\/tr>\n            <\/tbody>\n          <\/table>\n        <\/div>\n        <p class=\"nit-pg-table-note\">On narrow screens, swipe horizontally across the table. These are diagnostic clues, not definitive diagnoses. Similar symptoms may have different causes.<\/p>\n      <h3>Case study: the heading loads, but the image is absent<\/h3>\n      <p>If the HTML document loaded successfully but the image request returned 404, that is evidence about the image resource\u2014not proof that DNS failed.<\/p>\n      <h3>Case study: a certificate warning appears<\/h3>\n      <p>The browser may stop before ordinary protected HTTP communication. This is different from receiving an HTTP 404 response. Check the hostname and follow the browser&#8217;s safety guidance.<\/p>\n      <h3>Case study: the homepage looks right but buttons fail<\/h3>\n      <p>The document and styling may be present while JavaScript or an application request is malfunctioning. A 200 response for the HTML does not establish that the interface works.<\/p>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"evidence-challenge\" aria-labelledby=\"evidence-challenge-heading\">\n          <p class=\"nit-pg-eyebrow\">Think like a technician<\/p>\n          <h2 id=\"evidence-challenge-heading\">Three short evidence challenges<\/h2>\n            <div class=\"nit-curriculum-grid\">\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">CHALLENGE A<\/span>\n            <h3>One page, mixed results<\/h3>\n            <p>The HTML is 200, but a stylesheet is 404. The correct conclusion is that the document succeeded while a styling resource failed.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">CHALLENGE B<\/span>\n            <h3>Two requests, one page<\/h3>\n            <p>The first request returns 301, then another returns 200. The redirect may be a normal step rather than an outage.<\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">CHALLENGE C<\/span>\n            <h3>A cached second visit<\/h3>\n            <p>A stylesheet loads from cache the second time. That does not prove the website moved or that networking stopped working.<\/p>\n          <\/article>\n        <\/div>\n      <p>Practise the sequence <strong>observe \u2192 identify evidence \u2192 explain what it supports \u2192 avoid unsupported conclusions<\/strong>. It is a useful habit in web development, technical support and cybersecurity.<\/p>\n        <\/section>\n\n    <section class=\"nit-section-panel\" id=\"faq\" aria-labelledby=\"faq-heading\">\n          <p class=\"nit-pg-eyebrow\">Further questions<\/p>\n          <h2 id=\"faq-heading\">Frequently asked questions<\/h2>\n            <div class=\"nit-faq\">\n        <details class=\"nit-faq__item\">\n          <summary>Can a website open without a fresh DNS lookup?<\/summary>\n          <div class=\"nit-faq__answer\"><p>Yes. The browser or operating system may already have usable DNS information, an existing connection or a cached resource.<\/p><\/div>\n        <\/details>\n        <details class=\"nit-faq__item\">\n          <summary>Does one webpage always contact one server?<\/summary>\n          <div class=\"nit-faq__answer\"><p>No. A webpage may request content from several hosts, including CDNs or third-party services.<\/p><\/div>\n        <\/details>\n        <details class=\"nit-faq__item\">\n          <summary>What is the difference between a DNS error and 404 Not Found?<\/summary>\n          <div class=\"nit-faq__answer\"><p>DNS failure can prevent hostname resolution. A 404 is an HTTP response from a server indicating that the requested resource was not found.<\/p><\/div>\n        <\/details>\n        <details class=\"nit-faq__item\">\n          <summary>Does HTTPS guarantee that a website is legitimate?<\/summary>\n          <div class=\"nit-faq__answer\"><p>No. HTTPS protects communication; it does not guarantee that the operator or content is trustworthy.<\/p><\/div>\n        <\/details>\n        <details class=\"nit-faq__item\">\n          <summary>Can a website display content without JavaScript?<\/summary>\n          <div class=\"nit-faq__answer\"><p>Yes. HTML and CSS can display content without JavaScript, although some applications require JavaScript for key functionality.<\/p><\/div>\n        <\/details>\n        <details class=\"nit-faq__item\">\n          <summary>Does the Network panel show every packet?<\/summary>\n          <div class=\"nit-faq__answer\"><p>No. It primarily presents browser-level network requests and available timings, not a complete packet capture.<\/p><\/div>\n        <\/details>\n        <details class=\"nit-faq__item\">\n          <summary>Why might a page work while offline?<\/summary>\n          <div class=\"nit-faq__answer\"><p>Some web applications can use previously saved resources or service workers. A normal page that requires a fresh request may not work offline.<\/p><\/div>\n        <\/details>\n      <\/div>\n        <\/section>\n\n    <section class=\"nit-pg-section\" id=\"learning\" aria-labelledby=\"learning-heading\">\n          <p class=\"nit-pg-eyebrow\">Keep learning<\/p>\n          <h2 id=\"learning-heading\">How this helps you study web development and cybersecurity<\/h2>\n            <p>Once you understand how a browser loads a page, you can connect several technical subjects. Frontend development explains how HTML, CSS and JavaScript build interfaces. Backend development explains request handling. Cybersecurity examines network traffic, authentication and encryption. Cloud engineering focuses on servers, DNS and supporting infrastructure.<\/p>\n        <div class=\"nit-curriculum-grid\">\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">WEB FOUNDATIONS<\/span>\n            <h3>HTML, CSS and JavaScript<\/h3>\n            <p><a href=\"https:\/\/niteducation.com\/resources\/html-css-javascript-in-web-development\/\">Explore how webpage structure, presentation and behaviour work together.<\/a><\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">APPLICATION COMMUNICATION<\/span>\n            <h3>APIs and web development<\/h3>\n            <p><a href=\"https:\/\/niteducation.com\/resources\/what-is-an-api-in-web-development\/\">Learn how frontend and backend applications exchange information.<\/a><\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">PRACTICAL PROJECT<\/span>\n            <h3>Build your first web app<\/h3>\n            <p><a href=\"https:\/\/niteducation.com\/resources\/how-to-build-your-first-web-app\/\">Apply browser and programming knowledge to an app.<\/a><\/p>\n          <\/article>\n          <article class=\"nit-curriculum-card\">\n            <span class=\"nit-curriculum-card__period\">SECURITY PRACTICE<\/span>\n            <h3>Cybersecurity projects<\/h3>\n            <p><a href=\"https:\/\/niteducation.com\/resources\/cybersecurity-projects-for-beginners\/\">Learn controlled networking and security investigation.<\/a><\/p>\n          <\/article>\n        <\/div>\n      <h3>The central idea to remember<\/h3>\n      <p>DNS helps locate the destination; networking carries communication; TLS protects HTTPS; HTTP exchanges resources; and the browser renders them into the visible page. When something fails, inspect evidence at the correct stage.<\/p>\n        <\/section>\n\n    <section class=\"nit-pg-enrol\" id=\"register\" aria-labelledby=\"register-heading\">\n      <div class=\"nit-pg-enrol__copy\">\n        <p class=\"nit-pg-eyebrow\">Learn by building<\/p>\n        <h2 id=\"register-heading\">Study Practical ICT at Newton Institute of Technology<\/h2>\n        <p>Understanding how the web works is a foundation for building and securing applications. Explore NIT training pathways in Full-Stack Software Development and Cybersecurity and develop your skills through structured learning and projects.<\/p>\n      <\/div>\n      <div class=\"nit-pg-enrol__details\" aria-label=\"Programme information\">\n        <p><span>Foundation<\/span><strong>Website and networking concepts<\/strong><\/p>\n        <p><span>Progress to<\/span><strong>Full-Stack Development<\/strong><\/p>\n        <p><span>Explore<\/span><strong>Cybersecurity and practical ICT<\/strong><\/p>\n      <\/div>\n      <div class=\"nit-pg-enrol__actions\">\n        <a class=\"nit-pg-button nit-pg-button--gold\" href=\"https:\/\/niteducation.com\/courses\/ict\">Explore NIT ICT Courses<\/a>\n        <a class=\"nit-pg-button nit-pg-button--outline\" href=\"https:\/\/niteducation.com\/resources\/full-stack-software-development-course\/\">Full-Stack Course Guide<\/a>\n      <\/div>\n    <\/section>\n\n    <section class=\"nit-sources\" id=\"references\" aria-labelledby=\"references-heading\">\n      <h2 id=\"references-heading\">Sources and further reading<\/h2>\n      <ol>\n        <li id=\"source-1\"><strong>MDN Web Docs.<\/strong> <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Learn_web_development\/Getting_started\/Web_standards\/How_the_web_works\" target=\"_blank\" rel=\"noopener\">How the Web Works<\/a>.<\/li>\n        <li id=\"source-2\"><strong>IETF.<\/strong> <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc1034.html\" target=\"_blank\" rel=\"noopener\">RFC 1034: Domain Names \u2014 Concepts and Facilities (1987)<\/a>.<\/li>\n        <li id=\"source-3\"><strong>IETF.<\/strong> <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc9110.html\" target=\"_blank\" rel=\"noopener\">RFC 9110: HTTP Semantics (2022)<\/a>.<\/li>\n        <li id=\"source-4\"><strong>IETF.<\/strong> <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc9114.html\" target=\"_blank\" rel=\"noopener\">RFC 9114: HTTP\/3 (2022)<\/a>.<\/li>\n        <li id=\"source-5\"><strong>IETF.<\/strong> <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc8446.html\" target=\"_blank\" rel=\"noopener\">RFC 8446: TLS Protocol Version 1.3 (2018)<\/a>.<\/li>\n        <li id=\"source-6\"><strong>IETF.<\/strong> <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc9111.html\" target=\"_blank\" rel=\"noopener\">RFC 9111: HTTP Caching (2022)<\/a>.<\/li>\n        <li id=\"source-7\"><strong>Chrome for Developers.<\/strong> <a href=\"https:\/\/developer.chrome.com\/docs\/devtools\/network\/reference\/\" target=\"_blank\" rel=\"noopener\">Network Features Reference<\/a>.<\/li>\n        <li id=\"source-8\"><strong>MDN Web Docs.<\/strong> <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/Performance\/Guides\/How_browsers_work\" target=\"_blank\" rel=\"noopener\">Populating the Page: How Browsers Work<\/a>.<\/li>\n      <\/ol>\n      <p>Reviewed: 13 November 2026 \u00b7 Newton Institute of Technology Editorial Team.<\/p>\n    <\/section>\n\n  <\/div>\n<\/article>\n","protected":false},"excerpt":{"rendered":"<p>ICT Foundations What Happens When You Type a Website Address Into Your Browser? DNS \u2192 HTTPS \u2192 web servers \u2192 your screen Follow a URL from the address bar to a visible webpage. Understand every major stage, then investigate real website requests using Chrome DevTools. See the six steps Try the browser lab From address [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[30],"tags":[866,865,864],"class_list":["post-3849","post","type-post","status-publish","format-standard","hentry","category-ict","tag-dns-explained-for-beginners","tag-how-a-website-loads","tag-what-happens-when-you-type-a-url"],"_links":{"self":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3849","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/comments?post=3849"}],"version-history":[{"count":2,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3849\/revisions"}],"predecessor-version":[{"id":3868,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3849\/revisions\/3868"}],"wp:attachment":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/media?parent=3849"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/categories?post=3849"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/tags?post=3849"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}