Allowed
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
Grade B #4 of 73
Good website security
The main protections are in place, with a few settings left to improve.
B87/100
Secure connection
Strong40/40
Browser protections
Weak25/30
Domain protection
Weak7/15
Known threats
Strong15/15
Fix these first
- 1
DNSSEC
0/8To earn 8/8, enable DNSSEC at the DNS provider and publish its DS record through the registrar; then confirm the delegation validates without errors.
- 2
Referrer policy
0/5To earn 5/5, send Referrer-Policy: strict-origin-when-cross-origin. no-referrer, same-origin, and strict-origin also receive full points.
Strongest results
-
HTTPS response
15/15HTTPS returned status 200.
-
Valid TLS certificate
10/10The TLS certificate is valid for this domain.
-
Content security policy
10/10An enforced Content-Security-Policy limits script sources.
All 15 security checks
Every result is shown, with what it means and how to fix it.
Working 15/15
HTTPS response
HTTPS returned status 200.
Working 10/10
Valid TLS certificate
The TLS certificate is valid for this domain.
Working 5/5
HTTP redirects to HTTPS
HTTP redirects to HTTPS.
Working 5/5
Modern TLS
TLSv1.3 was negotiated.
Working 5/5
Strict transport security
Strict-Transport-Security covers at least 180 days.
Working 10/10
Content security policy
An enforced Content-Security-Policy limits script sources.
Working 5/5
Frame protection
The response limits which sites may frame it.
Working 5/5
Content type protection
Content type sniffing is disabled.
Needs attention 0/5
Referrer policy
Referrer-Policy is missing.
To earn 5/5, send Referrer-Policy: strict-origin-when-cross-origin. no-referrer, same-origin, and strict-origin also receive full points.
Working 5/5
Browser permissions policy
Common sensitive browser capabilities are disabled by default.
Needs attention 0/8
DNSSEC
DNSSEC validation data was not found.
To earn 8/8, enable DNSSEC at the DNS provider and publish its DS record through the registrar; then confirm the delegation validates without errors.
Working 7/7
Certificate authority restriction
CAA records restrict certificate issuance.
Working 6/6
Known malware reports
No active malware-distribution URL was reported.
Working 5/5
Threat-blocking DNS
3 threat-protection resolvers returned the domain.
Working 4/4
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/whatsapp.com/">
<img src="https://requestguard.com/domain/whatsapp.com/badges/security.svg" alt="Website security grade for whatsapp.com" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a>Embed code
<a href="https://requestguard.com/domain/whatsapp.com/#infrastructure">
<img src="https://requestguard.com/domain/whatsapp.com/badges/location.svg" alt="Network location for whatsapp.com" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a>Embed code
<a href="https://requestguard.com/domain/whatsapp.com/">
<img src="https://requestguard.com/domain/whatsapp.com/badges/trust.svg" alt="Trust badge for whatsapp.com" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a>Embed code
<a href="https://requestguard.com/domain/whatsapp.com/#whois">
<img src="https://requestguard.com/domain/whatsapp.com/badges/domain-rating.svg" alt="Domain Rating for whatsapp.com" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a> Use these results through the API
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
Clear
Automated crawler access
The identified crawler received HTTP 200 for the homepage.
Review
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.
Clear
robots.txt homepage rule
No robots.txt rule blocking Googlebot from the homepage was found.
Clear
Canonical URL
The canonical URL stays on whatsapp.com and matches the homepage path.
Clear
Search-readable HTML
The initial HTML contains a title and visible page content.
Clear
Sitemap discovery
robots.txt declares 1 sitemap.
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 18.1 years ago
Registration history and published ownership records. Domain age and Domain Rating are context, not a security verdict.
Registrar
Registration dates
Domain age
18.1 years
Created
Sep 4, 2008
Updated
Sep 20, 2026
Expires
Sep 4, 2034
Registrant
Name Domain Admin
Organization WhatsApp LLC
Email domain@fb.com
Phone +1.4089405686
Location 
Menlo Park, CA, US
Menlo Park, CA, US Domain status
Registry status codes — green means the owner locked out unauthorized changes
Delete locked Transfer locked Update locked Registry delete lock Registry transfer lock Registry update lock
Checked
Reputation & DNS filtering
Resolver behavior, domain datasets, and server-IP evidence
No threat match
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
Allowed
Family / content
Content and security policy
Allowed
Reputation datasets
URL and domain-list evidence, separate from resolver policy
URLhaus No match
Reported malware-distribution URLs
SURBL (via URLhaus) Unavailable
URLhaus metadata; this is not a direct SURBL query
Spamhaus DBL (via URLhaus) Unavailable
URLhaus metadata; this is not a direct Spamhaus DBL query
Server-IP DNSBL checks & threat feeds 
57.144.111.32
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
Unavailable
Unavailable
Unavailable
Unavailable
Unavailable
Unavailable
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