Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BDNS Records1 A records, 18 ms lookupREVIEW
| A | 150.171.109.146 |
| AAAA | 2603:1061:14:91::1 |
| CNAME | mr-z01.tm-azurefd.net |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
BRedirect Chain2 redirect(s), 110 ms totalREVIEW
https://www.technet.com
50 ms · HTTP/1.1
https://learn.microsoft.com
48 ms · HTTP/1.1
https://learn.microsoft.com/en-us/
13 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.technet.com | 301 | 50 ms | HTTP/1.1 | |
| 2 | https://learn.microsoft.com | 302 | 48 ms | HTTP/1.1 | |
| 3 | https://learn.microsoft.com/en-us/ | 200 | 13 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<!DOCTYPE html>
<html
class="layout layout-single welcome default-focus"
lang="en-us"
dir="ltr"
data-authenticated="false"
data-auth-status-determined="false"
data-target="docs"
x-ms-format-detection="none"
>
<head>
<title>Microsoft Learn: Build with answers in reach</title>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="color-scheme" content="light dark" />
<meta name="description" content="Find official documentation, practical know-how, and expert guidance for builders working and troubleshooting in Microsoft products." />
<!-- Non-customizable open graph and sharing-related metadata -->
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:site" content="@MicrosoftLearn" />
<meta property="og:type" content="website" />
<meta property="og:image:alt" content="Microsoft Learn" />
<meta property="og:image" content="https://learn.microsoft.com/en-us/media/open-graph-image.png" />
<!-- Page specific open graph and sharing-related metadata -->
<meta property="og:title" content="Microsoft Learn: Build with answers in reach" />
<meta property="og:description" content="Find official documentation, practical know-how, and expert guidance for builders working and troubleshooting in Microsoft products." />
<meta name="platform_id" content="921fc462-a2ae-c9d6-f17d-ebcb806eacac" />
<meta name="locale" content="en-us" />
<meta name="page_type" content="Docs" />
<!--page specific meta tags-->
<!-- custom meta tags -->
<!-- assets and js globals -->
<link rel="stylesheet" href="/static/assets/0.4.03396.7743-19995e1d/styles/site.css" />
<script src="https://wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js"></script>
<script src="https://js.monitor.azure.com/scripts/c/ms.jsll-4.min.js"></script>
<script src="/_themes/docs.theme/master/en-us/_themes/global/deprecation.js"></script>
<!-- msdocs global object -->
<script id="msdocs-script">
var msDocs = {
"environment": {
"accessLevel": "online",
"azurePortalHostname": "portal.azure.com",
"reviewFeatures": false,
"supportLevel": "production",
"systemContent": true,
"siteName": "learn",
"legacyHosting": false
},
"data": {
"contentLocale": "en-us",
"contentDir": "ltr",
"userLocale": "en-us",
"userDir": "ltr",
"pageTemplate": "Welcome",
"brand": "",
"context": {},
"standardFeedback": false,
"showFeedbackReport": false,
"feedbackHelpLinkType": "",
"feedbackHelpLinkUrl": "",
"feedbackSystem": "",
"feedbackGitHubRepo": "",
"feedbackProductUrl": "",
"extendBreadcrumb": false,
"isEditDisplayable": false,
"isPrivateUnauthorized": false,
"hideViewSource": false,
"isPermissioned": false,
"hasRecommendations": false,
"contributors": []
},
"functions": {}
};;
</script>
<!-- base scripts, msdocs global should be before this -->
<script src="/static/assets/0.4.03396.7743-19995e1d/scripts/en-us/index-docs.js"></script>
<!-- json-ld -->
</head>
<body
id="body"
data-bi-name="body"
class="layout-body "
lang="en-us"
dir="ltr"
>
<header class="layout-body-header">
<div class="header-holder has-default-focus">
<a
href="#main"
style="z-index: 1070"
class="outline-color-text visually-hidden-until-focused position-fixed inner-focus focus-visible top-0 left-0 right-0 padding-xs text-align-center background-color-body"
>
Skip to main content
</a>
<div hidden id="cookie-consent-holder" data-test-id="cookie-consent-container"></div>
<!-- Unsupported browser warning -->
<div
id="unsupported-browser"
style="background-color: white; color: black; padding: 16px; border-bottom: 1px solid grey;"
hidden
>
<div style="max-width: 800px; margin: 0 auto;">
<p style="font-size: 24px">This browser is no longer supported.</p>
<p style="font-size: 16px; margin-top: 16px;">
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
</p>
<div style="margin-top: 12px;">
<a
href="https://go.microsoft.com/fwlink/p/?LinkID=2092881 "
style="background-color: #0078d4; border: 1px solid #0078d4; color: white; padding: 6px 12px; border-radius: 2px; display: inline-block;"
>
Download Microsoft Edge
</a>
<a
href="https://learn.microsoft.com/en-us/lifecycle/faq/internet-explorer-microsoft-edge"
style="background-color: white; padding: 6px 12px; border: 1px solid #505050; color: #171717; border-radius: 2px; display: inline-block;"
>
More info about Internet Explorer and Microsoft Edge
</a>
</div>
</div>
</div>
<!-- site header -->
<div
id="ms--site-header"
data-test-id="site-header-wrapper"
itemscope="itemscope"
itemtype="http://schema.org/Organization"
>
<div
id="ms--mobile-nav"
class="site-header display-none-tablet padding-inline-none gap-none"
data-bi-name="mobile-header"
data-test-id="mobile-header"
></div>
<div
id="ms--primary-nav"
class="site-header display-none display-flex-tablet"
data-bi-name="L1-header"
data-test-id="primary-header"
></div>
<div
id="ms--secondary-nav"
class="display-none"
data-bi-name="L2-header"
data-test-id="secondary-header"
hidden
></div>
</div>
<!-- banner -->
<div data-banner>
<div id="disclaimer-holder"></div>
</div>
<!-- banner end -->
</div>
</header>
<main
id="main"
role="main"
class="layout-body-main "
data-bi-name="content"
lang="en-us"
dir="ltr"
>
<div id="ms--homepage-container">
<section
id="ms--welcome-hero"
data-bi-name="hero"
class="hero hero-image gradient-border-right gradient-border-body-accent background-color-body-accent"
style="--hero-background-image-light: url("/media/home-and-directory/home-hero_light.png"); --hero-background-image-dark: url("/media/home-and-directory/home-hero_dark.png");"
>
<div class="hero-content">
<h1 class="title is-1 gradient-text-vivid padding-bottom-sm margin-bottom-none">
Learning for everyone, everywhere
</h1>
<p>Explore Microsoft product documentation, training, credentials, Q&A, code references, and shows.</p>
<div id="form-wrapper" class="margin-top-sm">
<form
method="GET"
id="welcome-search-form-replacement"
name="welcome-search-form"
role="search"
action="/search"
>
<div class="columns is-mobile is-gapless">
<div class="column">
<div id="autocomplete-replacement" class="autocomplete display-block">
<div class="control">
<input
role="combobox"
id="facet-search-input"
class="autocomplete-input input control input-lg"
type="search"
aria-label="Search"
aria-controls="autocomplete-list"
aria-expanded="false"
placeholder="Search Microsoft Learn"
data-bi-name="home-search"
/>
</div>
</div>
</div>
<div class="column is-narrow">
<button
class="button button-primary button-filled button-lg margin-left-xxs"
type="submit"
data-bi-name="hero-search-button"
>
<span class="icon" aria-hidden="true">
<span class="docon docon-search"></span>
</span>
<span>Search</span>
</button>
</div>
</div>
</form>
</div>
</div>
</section>
<section id="popular-section" class="uhf-container" data-bi-name="popular-section">
<div class="padding-block-lg">
<h2 class="title is-2 text-align-center-tablet">Popular technical resources and training</h2>
<ul class=" grid is-3 gap-md gap-lg-desktop margin-top-lg">
<li class="grid-item">
<article data-bi-name="popular-card" class="card position-relative">
<div class="card-content">
<h3 class="card-title color-text font-size-xl margin-bottom-sm">
Discover AI, Azure, and Copilot essentials
</h3>
<p class="card-content-description color-text-subtle margin-bottom-sm">
Develop knowledge and skills faster with the latest resources and expert insights.
</p>
<div class="margin-top-sm">
<div class="media align-items-center">
<div class="media-left">
<img
aria-hidden="true"
class="card-template-icon"
src="/media/common/ai-microchip.svg"
loading="lazy"
/>
</div>
<div class="media-content">
<a href="/ai" class="has-external-link-indicator card-title">Artificial Intelligence</a>
</div>
</div>
</div>
<div class="margin-top-sm">
<div class="media align-items-center">
<div class="media-left">
<img
aria-hidden="true"
class="card-template-icon"
src="/media/logos/logo_azure.svg"
loading="lazy"
/>
</div>
<div class="media-content">
<a href="/azure" class="has-external-link-indicator card-title">Azure</a>
</div>
</div>
</div>
<div class="margin-top-sm">
<div class="media align-items-center">
<div class="media-left">
<img
aria-hidden="true"
class="card-template-icon"
src="/media/logos/logo_copilot.svg"
loading="lazy"
/>
</div>
<div class="media-content">
<a href="/copilot" class="has-external-link-indicator card-title">Microsoft Copilot</a>
</div>
</div>
</div>
</div>
<div class="card-footer card-footer-left border-top-none">
<div class="card-footer-item padding-block-xs">
<a
href="/docs"
class="font-size-s
BTLS Certificate Expiry & Recommendations169 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligencetechnet.com — via Nom-iq Ltd. dba COM LAUDE, 27 years, 6 months old, hosted on Microsoft AzurePASS
260 days
March 3, 2027
169 days
Issued by Microsoft Corporation
27 years, 6 months
Registered March 3, 1999
Not enabled
Protects against DNS spoofing
Microsoft Azure
ASN AS8075
20.76.201.171
Nom-iq Ltd. dba COM LAUDE
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice