IPDebrief

172.203.134.70

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.

Threat Intelligence Briefing: IP Address 172.203.134.70/32

Summary:

The IP address 172.203.134.70/32 has been analyzed using a range of intelligence-gathering tools. This private IP address resides within a non-routable IP range (172.16.0.0 to 172.31.255.255), typically used for internal network purposes. The following analysis provides an overview of the IP's profile, observation history, and neighborhood data.

Profile and Ownership:

Observation History:

Relationships and Network Associations:

Neighborhood Data:

Actionable Insights:

Conclusion:

IP address 172.203.134.70/32 is a private IP address used within an internal network. It exhibits typical behavior consistent with internal network operations, with no recorded anomalies or security incidents. Continuous monitoring and regular security assessments are recommended to maintain the integrity and security of the network environment.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionVA
CityWashington
Timezoneβ€”
Latitude38.71
Longitude-78.15

🏒 Ownership & Registration

OrganizationDivya Quamara
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
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
27%
23
routing
8%
11
services
8%
11
ownership
24%
23
reputation
26%
13
geolocation
33%
23
Overall21%914
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-13 19:04:03 UTC
Last Seen2026-06-27 23:44:10 UTC
Profile Built2026-06-28 17:48:36 UTC
Data FreshnessLive
Signal Types17
Total Observations21
πŸ” 17 signal types Β· 21 observations collected
This report is generated from 17+ 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.