IPDebrief

3.5.130.229

IP Intelligence Dossier
Your IP: 216.73.217.34
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP address 3.5.130.229/32 was identified as a web server hosted within the Amazon Data Services Northern Virginia network (ASN 16509) under the AMAZON-S3 block. The address resolved to the PTR hostname s3.us-east-2.amazonaws.com and presented an AmazonS3 server banner on ports 80, 443, and 8080. While the overall risk score remained low at 25, the profile indicated a "Suspicious Host" classification with a recommendation to monitor due to signal contradictions. Geolocation data placed the host in Columbus, Ohio, but RTT physics measurements contradicted this claim, recording a distance of 6580.9km against a minimum possible RTT of 35ms. The control plane showed one DNSBL listing despite a zero blacklist count in the threat indicators. No known campaigns, attacker signatures, or active attack behavior were observed during the period from September 5 to September 18, 2026. The IP remained within the 3.5.130.0/24 BGP prefix.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionOH
CityColumbus
TimezoneAmerica/New_York
Latitude39.96
Longitude-83.00

🏒 Ownership & Registration

OrganizationAmazon Data Services Northern Virginia
ASNAS16509
Network NameAMAZON-S3
CIDR Block3.5.0.0/16
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRs3.us-east-2.amazonaws.com
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamess3.us-east-2.amazonaws.com

πŸ” DNS Hygiene

Hygiene Score40% (Fair)
SPFPresent
DMARCPresent
FCrDNSNot verified
DNSSECNot signed
CAANot configured

☁️ Network Classification

InfrastructureUnknown
Service PurposeWeb Server
Network TierHosting β€” Infrastructure provider without advanced routing
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpβ€”
443httpstcpβ€”
8080http-alttcpβ€”
Closed Ports22, 25, 3389, 8443 (3 open / 7 scanned)
ServerAmazonS3
HTTP Titleβ€”

πŸ” TLS Certificate

πŸ”’
CN=*.s3.us-east-2.amazonaws.com
Issued by CN=Amazon RSA 2048 M01, O=Amazon, C=US
Self-signed: No
SANs*.s3.us-east-2.amazonaws.coms3.us-east-2.amazonaws.com*.s3.amazonaws.com*.s3-accesspoint.dualstack.us-east-2.amazonaws.com*.s3-control.us-east-2.amazonaws.coms3.dualstack.us-east-2.amazonaws.coms3-control.dualstack.us-east-2.amazonaws.com*.s3-deprecated.us-east-2.amazonaws.com*.s3.dualstack.us-east-2.amazonaws.coms3-control.us-east-2.amazonaws.com
Valid From2026-07-12T00:00:00+00:00
Valid Until2027-01-25T23:59:59+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_128_GCM_SHA256
Signature Algorithmsha256RSA
Validity Period197 days
Serial Number075F79C2B32303609A25DE8583D1F8E2
Thumbprint3DBB9A8EA89C1DD8DF473C1CF9666DAEB2C21F70

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
27%
23
routing
13%
11
services
33%
24
ownership
27%
23
reputation
13%
12
geolocation
27%
23
Overall23%1016
Coverage: 5/6 dimensions Β· Data sufficiency: partial
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-09-05 08:31:01 UTC
Last Seen2026-09-18 21:43:28 UTC
Profile Built2026-09-18 21:51:32 UTC
Data FreshnessLive
Signal Types23
Total Observations31
πŸ” 23 signal types Β· 31 observations collected
This report is generated from 23+ 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.