IPDebrief

2a02:2908:4400:183a:b70c:d0c7:349e:3342

IP Intelligence Dossier
Your IP: 216.73.217.11
{ } JSON 🔧 Full Actions API
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# IP Intelligence Briefing

Target: 2a02:2908:4400:183a:b70c:d0c7:349e:3342/128

Date: 2026-10-04

Risk Score: 60/100 (Moderate)

Classification: Active Attacker

---

## Executive Summary

IP 2a02:2908:4400:183a:b70c:d0c7:349e:3342, belonging to Nawras-NOC (ASN 50010), demonstrated active attacker behavior during the observation period. The IP triggered a honeypot trap via credential-stuffing activity and was classified as a direct attack source. The IP is located in Muscat, Oman, and operates within the OM-QATARITELECOM-20101110 network block.

## Threat Assessment

Attack Indicators

Network Profile

Historical Activity

Neighborhood Context

The /48 subnet (2a02:2908:4400:183a:b70c:d0c7:349e:3342/48) shows:

## Recommended Actions

Immediate Mitigation

Block the IP address at all perimeter defenses. Implement the following rules:

iptables:

```

iptables -A INPUT -s 2a02:2908:4400:183a:b70c:d0c7:349e:3342 -j DROP

```

nftables:

```

nft add rule inet filter input ip saddr 2a02:2908:4400:183a:b70c:d0c7:349e:3342 drop

```

nginx:

```

deny 2a02:2908:4400:183a:b70c:d0c7:349e:3342;

```

pfSense:

```

2a02:2908:4400:183a:b70c:d0c7:349e:3342/32

```

Cloudflare WAF:

```json

{"description":"Block 2a02:2908:4400:183a:b70c:d0c7:349e:3342 — IPDebrief risk score 60","action":"block","filter":{"expression":"ip.src eq 2a02:2908:4400:183a:b70c:d0c7:349e:3342"}}

```

AWS WAF:

```json

{"Addresses":["2a02:2908:4400:183a:b70c:d0c7:349e:3342/32"],"Description":"IPDebrief risk 60"}

```

Ongoing Monitoring

## Intelligence Notes

The IP originated from a legitimate Omani telecommunications provider but exhibited attacker behavior consistent with credential-stuffing campaigns. The honeypot hit indicates the attacker attempted to probe authentication mechanisms. No open services or hosting infrastructure were detected, suggesting this IP was used for scanning and exploitation attempts rather than serving as a command-and-control infrastructure.

The subnet neighborhood analysis shows zero abuse density, indicating this activity was isolated to this single IP address. No other IPs in the /48 block have been flagged as malicious during the observation window.

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

🌍 Geolocation

Country🇴🇲 OM
RegionMuscat
CityMuscat
Timezone—
Latitude23.58
Longitude58.40
🛡️ Platform Security History
HoneypotTrap endpoint probes1
Total events: 1
Observed on 2026-06-29

🏢 Ownership & Registration

OrganizationNawras-NOC
ASNAS50010
Network NameOM-QATARITELECOM-20101110
CIDR Block—
RIRLACNIC
CountryOM
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 Score0% (None)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECNot signed
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—

🛡️ Public Network Snapshot

Origin ASNAS50010
Network Prefix2a02:2908:4400::/48
Route mappingFound

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
13%
11
routing
0%
00
services
0%
00
ownership
25%
12
reputation
13%
12
geolocation
13%
11
Overall11%46
Coverage: 4/6 dimensions · Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

📅 Observation Timeline 🔄 Live

First Seen2026-06-29 04:53:11 UTC
Last Seen2026-10-09 04:57:47 UTC
Profile Built2026-10-09 04:59:50 UTC
Data FreshnessLive
Signal Types19
Total Observations19
🔍 19 signal types · 19 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

❓ Frequently Asked Questions About 2a02:2908:4400:183a:b70c:d0c7:349e:3342

Who owns the IP address 2a02:2908:4400:183a:b70c:d0c7:349e:3342?

2a02:2908:4400:183a:b70c:d0c7:349e:3342 is registered to Nawras-NOC. Registration is held at LACNIC.

Where is 2a02:2908:4400:183a:b70c:d0c7:349e:3342 located?

Geolocation data places 2a02:2908:4400:183a:b70c:d0c7:349e:3342 in Muscat, Muscat, OM. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.

Is 2a02:2908:4400:183a:b70c:d0c7:349e:3342 malicious or safe?

2a02:2908:4400:183a:b70c:d0c7:349e:3342 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.

🏘️ Related IP Addresses

Nearby addresses

Browse related networks

ℹ️ 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.