IPDebrief

111.70.33.248

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

Date: 2026-06-17

---

**1. Core Profile**

- Listed in 3/8 DNSBLs (high-risk spam/abuse lists)

- No TLS certificate detected

- Server fingerprint: `lighttpd/1.4.30` (older version)

---

**2. Observation History**

- Detected in 5 DNSBL listings (high-severity threats)

- HTTP server responded with status 200, no HSTS or CSP headers

- TLS scan showed no active certificate

- First observed on 2026-06-02; no persistent malicious behavior noted

- No significant ownership or threat persistence over time

---

**3. Relationships**

- Linked to `111-70-33-248.emome-ip.hinet.net` (hinet.net)

- SPF record exists (`v=spf1 redirect=spf.ms.hinet.net`), but no DMARC

- Part of `111.70.33.0/24` subnet with moderate abuse density (0.5)

---

**4. Neighborhood Analysis**

- 111.70.33.163: Risk score 80 (High)

- 111.70.33.165: Risk score 80 (High)

- 111.70.33.194: Risk score 70 (Medium)

- 111.70.33.217: Risk score 55 (Low)

---

**5. Recommendations**

1. Block the IP: Add to firewall rules (iptables/nftables) to mitigate potential threats.

2. Monitor Subnet: Track neighboring IPs (111.70.33.163, 111.70.33.165) for suspicious activity.

3. Check Server Configuration:

- Update `lighttpd` to a newer version (1.4.30 is outdated).

- Implement DMARC and HSTS for improved email and HTTPS security.

4. DNSBL Scrutiny: Investigate why this IP is listed in DNSBLs; confirm if it’s a false positive or legitimate abuse.

---

Note: This IP is associated with a Taiwanese ISP (hinet.net). While the server appears legitimate, its DNSBL listings and outdated software warrant further investigation.

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

🌍 Geolocation

CountryπŸ‡ΉπŸ‡Ό Taiwan
Regionβ€”
Cityβ€”
TimezoneAsia/Taipei
Latitude23.70
Longitude120.96

🏒 Ownership & Registration

OrganizationUnknown
ASNAS17421
Network Nameβ€”
CIDR Block111.70.0.0/18
RIRβ€”
Countryβ€”
Abuse Contactβ€”

🌐 DNS Intelligence

PTR111-70-33-248.emome-ip.hinet.net
Forward ConfirmedYes β€” FCrDNS verified
Forward Hostnames111-70-33-248.emome-ip.hinet.net

πŸ” DNS Hygiene

Hygiene Score80% (Excellent)
SPFPresent
DMARCNot configured
FCrDNSVerified
DNSSECValid
CAAPresent

☁️ 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)
Serverlighttpd/1.4.30
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
32%
23
routing
13%
11
services
26%
23
ownership
19%
22
reputation
17%
12
geolocation
32%
23
Overall23%1014
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Recent

First Seen2026-05-07 23:03:31 UTC
Last Seen2026-06-26 14:30:51 UTC
Profile Built2026-06-27 07:11:33 UTC
Data FreshnessRecent
Signal Types23
Total Observations23
πŸ” 23 signal types Β· 23 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.