IPDebrief

107.175.33.240

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: 107.175.33.240

Date: 2026-05-31

---

**1. Core Profile**

---

**2. Observation History**

- Confirmed registration to HostPapa (arin).

- No open ports or services detected in scans.

- DNSBL listings (4/8 total) suggest potential spam or abuse risks.

- 50+ pulses detected (e.g., "malware," "phishing").

- Low confidence in network classification (non-CDN, non-VPN).

- Subnet `107.175.33.240/24` is clean, with no active/compromised siblings.

---

**3. Relationships**

- Linked to BGP network `CC-17` (HostPapa).

- Directly associated with `107-175-33-240-host.colocrossing.com`.

- No correlated IPs, campaigns, or certificates detected.

---

**4. Neighborhood**

---

**5. Recommendations**

---

Summary: This IP exhibits high risk due to DNSBL listings and pulse activity, but no direct malicious indicators are present. Its isolated nature and clean subnet suggest it may be a misconfigured or compromised host. SOC teams should prioritize monitoring DNS activity and network traffic associated with this IP.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionNY
CityBuffalo
Timezoneβ€”
Latitude42.89
Longitude-78.88

🏒 Ownership & Registration

OrganizationHostPapa
ASNAS36352
Network Nameβ€”
CIDR Blockβ€”
RIRARIN
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR107-175-33-240-host.colocrossing.com
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnames107-175-33-240-host.colocrossing.com

πŸ” DNS Hygiene

Hygiene Score60% (Good)
SPFPresent
DMARCPresent
FCrDNSNot verified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ 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
19%
22
routing
13%
11
services
19%
22
ownership
30%
23
reputation
13%
12
geolocation
19%
22
Overall19%1012
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-13 19:03:26 UTC
Last Seen2026-06-13 03:44:20 UTC
Profile Built2026-06-06 22:58:43 UTC
Data FreshnessLive
Signal Types20
Total Observations20
πŸ” 20 signal types Β· 20 observations collected
This report is generated from 20+ 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.