Infrastructure - https://office365.com BeaverCheck Audit

D

Crawlability

Action

robots.txt present, no sitemap

FIX

robots.txt present, no sitemap

robots.txt is present

Got: 102 bytes

robots.txt blocks all crawlers

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK

Size 102 B Sitemaps referenced 0 User-agents * Blocking Yes — all crawlers blocked

# Robots.txt file for office host
#


User-agent: *

Allow: /$

Allow: /office/url/

Disallow:/

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

D

CDN & Delivery

Action

No CDN detected

FIX

No CDN detected

A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

No IPv6 (AAAA) records found

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

No IPv6 Support

About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B

HTTP Probe Timing

Total 879 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

2 ms

TCP Connect

113 ms

TLS Handshake

648 ms

Time to First Byte

879 ms

Total Time

880 ms

Connection waterfall

DNS Lookup 2 ms TCP Connect 113 ms TLS Handshake 648 ms Server Processing 115 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

170 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

170

days left

0d 30d 60d 90d+

Recommended actions

Submit your domain to hstspreload.org to be added to the Chrome preload list
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

A+

DNS Records

2 A records, 17 ms lookup

PASS

2 A records, 17 ms lookup

Resolves to 2 IPv4 address(es)

Got: 20.119.0.28, 40.112.243.53

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info

No MX records — email not configured via DNS

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 17 ms

Got: 17 ms

A	20.119.0.28, 40.112.243.53
AAAA	—
CNAME	—
NS	ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info
MX	—
TXT	SPF v=spf1 include:spf.protection.outlook.com ~all google-site-verification=u9PqvuplbTIYlwiMAzJWnRRtHYoAlaTX5GMtRRXqWXA officeprodes.azurewebsites.net _ufamlucd6jp7xslb9wnr85vc03dxyqh
CAA	Lookup not available with standard resolver

Resolved in 17 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A

Redirect Chain

1 redirect(s), 758 ms total

PASS

1 redirect(s), 758 ms total

Single redirect

Got: https://office365.com → https://www.microsoft.com/microsoft-365?ms.url=office365com (301)

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://www.microsoft.com/microsoft-365?ms.url=office365com

Redirect overhead: 758 ms total

Got: 758 ms

Cross-domain redirect detected

https://office365.com

739 ms · HTTP/1.1

301

https://www.microsoft.com/microsoft-365?...

20 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://office365.com	301	739 ms	HTTP/1.1	Kestrel
2	https://www.microsoft.com/microsoft-365?...	302	20 ms	HTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

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

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.office365.com/

200https://office365.com/

Preferred variant: non-www

HTTP → HTTPS

301http://office365.com/ → https://www.microsoft.com/microsoft-365?ms.url=office365com

Consistent

A

Domain Intelligence

office365.com — via MarkMonitor Inc., 21 years, 1 months old, hosted on Microsoft Azure

PASS

office365.com — via MarkMonitor Inc., 21 years, 1 months old, hosted on Microsoft Azure

Domain expires in 65 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Jun 20, 2026

DNSSEC is not enabled

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Registrar: MarkMonitor Inc.

Registrar lock is NOT enabled

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.

Hosting: Microsoft Azure

Got: AS8075

Domain expiry

5 days

June 20, 2026

SSL certificate

170 days

Issued by Microsoft Corporation

Domain age

21 years, 1 months

Registered June 20, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

40.112.243.53

Registrar

MarkMonitor Inc.

Unlocked 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar MarkMonitor Inc.

Created June 20, 2005 (21 years, 1 months ago)

Expires June 20, 2026 (2 months)

Last Updated May 19, 2025

Name Servers ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info

DNSSEC Not enabled

Hosting

IP Address 40.112.243.53

ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)

Provider Microsoft Azure

Data source: rdap (0.7s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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