Domain intelligence
Security Report for
A closer look at this domain’s security, infrastructure, and public records. Findings first, with the evidence behind every result.
Explore the reportWebsite Security
HTTPS, browser protections, DNS controls and known threats
Good website security
The main protections are in place, with a few settings left to improve.
Secure connection
Strong40/40
Browser protections
Weak19/30
Domain protection
Strong15/15
Known threats
Strong15/15
Fix these first
- 1
Content security policy
4/10To earn 10/10, remove *, http:, https:, data:, 'unsafe-inline', and 'unsafe-eval' from script-src or its default-src fallback. Allow exact hosts and use per-request nonces or hashes for required inline scripts.
- 2
Browser permissions policy
0/5To earn 5/5, disable all three tested capabilities: Permissions-Policy: camera=(), microphone=(), geolocation=(). Add separate directives for capabilities the site intentionally allows.
Strongest results
-
HTTPS response
15/15HTTPS returned status 200.
-
Valid TLS certificate
10/10The TLS certificate is valid for this domain.
-
DNSSEC
8/8DNSSEC validation data was found.
All 15 security checks
Every result is shown, with what it means and how to fix it.
HTTPS response
HTTPS returned status 200.
Valid TLS certificate
The TLS certificate is valid for this domain.
HTTP redirects to HTTPS
HTTP redirects to HTTPS.
Modern TLS
TLSv1.3 was negotiated.
Strict transport security
Strict-Transport-Security covers at least 180 days.
Content security policy
Content-Security-Policy is enforced but allows broad script sources.
To earn 10/10, remove *, http:, https:, data:, 'unsafe-inline', and 'unsafe-eval' from script-src or its default-src fallback. Allow exact hosts and use per-request nonces or hashes for required inline scripts.
Frame protection
The response limits which sites may frame it.
Content type protection
Content type sniffing is disabled.
Referrer policy
Referrer-Policy uses strict-origin-when-cross-origin.
Browser permissions policy
Permissions-Policy is missing.
To earn 5/5, disable all three tested capabilities: Permissions-Policy: camera=(), microphone=(), geolocation=(). Add separate directives for capabilities the site intentionally allows.
DNSSEC
DNSSEC validation data was found.
Certificate authority restriction
CAA records restrict certificate issuance.
Known malware reports
No active malware-distribution URL was reported.
Threat-blocking DNS
3 threat-protection resolvers returned the domain.
Domain blocklists
The domain did not match the checked domain blocklists.
This dated automated check does not verify the business, its content, or every page. The score describes the configuration observed during this scan.
Badges and embed code
Embed code
<a href="https://requestguard.com/domain/cloud.microsoft/">
<img src="https://requestguard.com/domain/cloud.microsoft/badges/security.svg" alt="Website security grade for cloud.microsoft" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a> Embed code
<a href="https://requestguard.com/domain/cloud.microsoft/#infrastructure">
<img src="https://requestguard.com/domain/cloud.microsoft/badges/location.svg" alt="Network location for cloud.microsoft" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a> Embed code
<a href="https://requestguard.com/domain/cloud.microsoft/">
<img src="https://requestguard.com/domain/cloud.microsoft/badges/trust.svg" alt="Trust badge for cloud.microsoft" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a> Embed code
<a href="https://requestguard.com/domain/cloud.microsoft/#whois">
<img src="https://requestguard.com/domain/cloud.microsoft/badges/domain-rating.svg" alt="Domain Rating for cloud.microsoft" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a> API requests require a workspace key and a plan with Lookups access.
The hosted badge updates after a manual scan. A downloaded badge stays static and avoids contacting RequestGuard on page views.
Search visibility
Homepage signals that can affect crawling and indexing
Needs review
Some homepage signals need a closer look. Review the recommendations below.
6 homepage checks · Unscored
Observed request
Automated crawler access
The identified crawler received HTTP 200 for the homepage.
Indexing directives
No noindex directive was found in the captured part of the response, but the HTML exceeded the scan limit.
Keep robots metadata in the document head and confirm the rendered page with Google Search Console URL Inspection.
robots.txt homepage rule
No blocking homepage rule was found in the captured part of robots.txt, but the file exceeded the scan limit.
Keep the applicable Googlebot and wildcard rules concise, and confirm the complete robots.txt file does not block the homepage.
Canonical URL
The canonical URL stays on cloud.microsoft and matches the homepage path.
Search-readable HTML
The initial HTML contains a title and visible page content.
Sitemap discovery
No XML sitemap declaration or conventional /sitemap.xml response was found. A sitemap is optional, but it helps discovery for new sites.
Publish an XML sitemap and declare it in robots.txt or submit it in Google Search Console.
This is not a Google index lookup. RequestGuard tests public signals with an identified automated crawler. Only URL Inspection for a verified Google Search Console property can confirm Google's last crawl, selected canonical, and indexing decision.
Open Google's URL Inspection guideCached result
Public exposure
Sensitive files and public administrative interfaces
Not checked—run a website scan.
Checks 100 common paths and up to 50 technology-specific paths. Opening this report does not start exposure checks.
These are bounded, unauthenticated crawler observations, not a penetration test. A public login is not automatically a vulnerability. Secret values are discarded. Findings do not affect your security score.
Server Infrastructure
Resolved addresses, networks, and hosting providers
DNS Records
A, AAAA, MX, and resolving certificate hostnames, with other record types on demand
Email & DNS Security
MX, SPF, DMARC, DNSSEC, and CAA posture
WHOIS & Registrar
Registration details via RDAP
Registered 11.0 years ago
Registration history and published ownership records. Domain age and Domain Rating are context, not a security verdict.
Registrar
MarkMonitor Inc.
Registration dates
Domain age
11.0 years
Created
Sep 25, 2015
Updated
Sep 12, 2026
Expires
Sep 25, 2027
Registrant
Privacy protectedIdentity is hidden by a privacy service — standard practice under GDPR and similar laws, not on its own a sign of anything suspicious.
Some of the data in this object has been removed
Domain status
Registry status codes — green means the owner locked out unauthorized changes
Checked
Reputation & DNS filtering
Resolver behavior, domain datasets, and server-IP evidence
Resolver summary
No match found in 3 checked threat-protection resolvers.
Checked . No-match results apply only to the sources that returned comparable evidence.
Resolver filtering records provider behavior. It does not by itself prove that a domain is malicious.
Resolver matrix
Five public filtering policies compared with neutral DNS
Threat protection
Malware and phishing policy
Ads & tracking
Mixed privacy and security policy
Family / content
Content and security policy
Reputation datasets
URL and domain-list evidence, separate from resolver policy
Reported malware-distribution URLs
URLhaus metadata; this is not a direct SURBL query
URLhaus metadata; this is not a direct Spamhaus DBL query
Server-IP DNSBL checks & threat feeds
20.70.246.20
DNSBL and network-feed matches do not determine the domain verdict. Shared hosting, reverse proxies, and CDNs can put unrelated domains on the same address.
Barracuda
b.barracudacentral.org
SpamCop
bl.spamcop.net
UCEPROTECT L1
dnsbl-1.uceprotect.net
DroneBL
dnsbl.dronebl.org
NextDNS and other custom profiles are not tested because their result depends on enabled lists, security settings, and parental controls. Check the provider log for the exact rule.
Cached result