IPDebrief

4.228.83.111

IP Intelligence Dossier
Your IP: 216.73.216.123
{ } JSON ๐Ÿ”ง Full Actions API
๐Ÿค– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP Intelligence Briefing: 4.228.83.111

Date: 2026-06-09

---

**1. Core Profile**

---

**2. Observation History**

- DNSSEC validation issues noted (possibly misconfigured).

- Stable network role as Microsoft Azure infrastructure.

- No persistent malicious behavior or threat persistence.

---

**3. Relationships & Subnet**

- Strong ties to Microsoft Azure networks (MSFT).

- No connections to known malicious organizations or subnets.

- Abuse Density: 0% (clean subnet).

- Neighbors: 1 sibling IP (4.228.83.12) with low risk score (25/100).

---

**4. Security Recommendations**

- Increase logging verbosity for this IP and review recent activity.

- Monitor DNSSEC validation status due to potential misconfiguration.

- iptables: `iptables -A INPUT -s 4.228.83.111 -j DROP`

- Cloudflare WAF: Block IP with rule `ip.src eq 4.228.83.111`

- AWS WAF: Add `4.228.83.111/32` to a rule with description "IPDebrief risk 65".

---

**5. Conclusion**

The IP is a legitimate Microsoft Azure resource with no direct evidence of malicious activity. The moderate risk score may stem from DNSSEC issues or isolated anomalies. SOC teams should maintain monitoring for unusual behavior, especially given its cloud infrastructure role. No immediate blocking recommended, but enhanced logging is advised.

Source: IPDebrief Threat Intelligence Platform

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

๐ŸŒ Geolocation

Country๐Ÿ‡ง๐Ÿ‡ท Brazil
RegionSP
CitySão Paulo
TimezoneAmerica/Sao_Paulo
Latitude-23.55
Longitude-46.63

๐Ÿข Ownership & Registration

OrganizationMicrosoft Corporation
ASNAS8075
Network Nameโ€”
CIDR Blockโ€”
RIRARIN
Countryโ€”
Abuse ContactAvailable via RDAP

๐ŸŒ DNS Intelligence

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

๐Ÿ” DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

โ˜๏ธ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeFirewalled / No Services
Network TierHosting โ€” Infrastructure provider without advanced routing
CloudHosting

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Serverโ€”
HTTP Titleโ€”

๐Ÿ” TLS Certificate

๐Ÿ”’
No certificate
Issued by โ€”
N/A
SANsNone
Valid Fromโ€”
Valid Untilโ€”

๐ŸŽฏ Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
39%
23
routing
8%
11
services
15%
22
ownership
20%
23
reputation
22%
12
geolocation
33%
23
Overall23%1014
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-20 22:13:12 UTC
Last Seen2026-06-28 12:45:08 UTC
Profile Built2026-06-29 06:50:44 UTC
Data FreshnessLive
Signal Types19
Total Observations22
๐Ÿ” 19 signal types ยท 22 observations collected
This report is generated from 19+ 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 ๐Ÿ”ง Actions API ๐Ÿ“ง Enterprise Access

โ„น๏ธ 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.