IPDebrief

20.33.3.2

IP Intelligence Dossier
Your IP: 216.73.216.131

20.33.3.2 is an IPv4 address operated by Microsoft Azure, with approximate network location Washington, United States. It belongs to datacenter or hosting infrastructure. As of November 12, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.

{ } JSON

🌍 Geolocation

Country🇺🇸 United States
Location scopeApproximate network location. Distributed and anycast services can vary by observation point.
Anycast classificationUnverified (not proof of unicast)
RegionVA
CityWashington
TimezoneAmerica/New_York
Latitude38.71
Longitude-78.15

🏢 Ownership & Registration

Registered holderUnknown
ASN—
Network Name—
CIDR Block—
RIR—
Network registration country—
Abuse Contact—

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo — PTR hostname does not resolve back to this IP (weak signal)

DNS Posture

Results describe the queried names. SPF, DMARC and CAA are domain policies, not requirements for every IP. DNSSEC here describes reverse DNS; inconclusive validation does not mean unsigned.

Not assessed: 0 conclusive IP DNS checks.

spfNot checked
dmarcNot checked
fcrDnsNot checked
dnssecNot checked
caaNot checked

☁️ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeWeb Server
Network TierHosting — Infrastructure provider without advanced routing
CloudHosting

🔌 Services & Open Ports

PortServiceProtocolBanner
443httpstcp—
Closed Ports22, 25, 80, 3389, 8080, 8443 (1 open / 7 scanned)
Server—
HTTP Title—

🔐 TLS Certificate

Previously observed certificate has since expired; current certificate unknown. This describes the last probe, not a live check. An IP-targeted handshake does not establish the certificate served for every hostname.
🔒
CN=spoc.norton.com, O=Gen Digital Inc., S=Arizona, C=US
Issued by CN=Sectigo Public Server Authentication CA OV R36, O=Sectigo Limited, C=GB
Self-signed: No
SANsspoc.norton.comspoc-pool-gtm.norton.comspoc-pool.norton.comspoc.avast.comspoc.avg.comspoc.avira.comspocnotify.avast.comspocnotify.avg.comspocnotify.avira.comspocnotify.norton.com
Valid From2025-11-03T00:00:00+00:00
Valid Until2026-11-03T23:59:59+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period365 days

🛡️ Public Network Snapshot

Origin ASNAS8069
Network Prefix20.33.3.0/24
Route mappingFound
HSTSNot detected
CSPNot detected
HTTP/2Not detected

📅 Observation Timeline 🔄 Stale

First Seen2026-10-05 21:54:03 UTC
Last Seen2026-10-05 21:54:03 UTC
Profile Built2026-11-12 03:34:55 UTC
Data FreshnessStale
Signal Types11
Total Observations11
🔍 11 signal types · 11 observations collected
This report is generated from 11+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API 📧 Enterprise Access

❓ Frequently Asked Questions About 20.33.3.2

Where is 20.33.3.2 located?

Geolocation data places 20.33.3.2 in Washington, VA, United States. The local time zone is America/New_York. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.

Is 20.33.3.2 malicious or safe?

20.33.3.2 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.

What ports are open on 20.33.3.2?

Responsive ports observed on 20.33.3.2 include 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.

Is 20.33.3.2 a VPN, proxy, or data center address?

20.33.3.2 is classified as cloud infrastructure and hosting infrastructure based on network ownership and behavioural analysis.

🏘️ Related IP Addresses

Browse related networks

Microsoft Azure IP ranges🇺🇸 United StatesNetwork directory

ℹ️ About This Report

All data shown is publicly available network metadata — IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.