IPDebrief

91.240.254.172

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

Date: 2026-06-11

---

**1. Core Profile**

- Reported: Newark, NJ, US (via geolocation).

- Conflict: Historical observations (June 2, 2026) indicate Amsterdam, Netherlands. This discrepancy may signal spoofed geolocation, misconfigured routing, or multi-homed infrastructure.

---

**2. Threat & Behavior**

---

**3. Historical Observations**

- June 2, 2026: Amsterdam, Netherlands (maxmind-geolite2).

- June 11, 2026: Newark, NJ, US.

- Implication: Potential IP spoofing, misconfigured geolocation, or multi-region use.

---

**4. Relationships & Neighbors**

- /24 Subnet: *91.240.254.0/24* (0 active neighbors reported).

- Abuse Density: 0% (no malicious neighbors).

---

**5. Recommendations**

1. Geolocation Verification: Investigate the geolocation discrepancy. Validate if the IP is part of a multi-homed setup or if spoofing is occurring.

2. Monitor Routing Stability: Track BGP route changes for *91.240.254.0/24* due to instability.

3. DNS & Email Security: Ensure DNSSEC and email authentication (SPF/DKIM) are configured for associated domains.

4. Subnet Analysis: Confirm the absence of neighbors in *91.240.254.0/24* is intentional (e.g., single-host use) or indicative of a misconfigured network.

Conclusion: No immediate threat detected, but geolocation inconsistencies and routing instability warrant further investigation.

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

๐ŸŒ Geolocation

Country๐Ÿ‡ณ๐Ÿ‡ฑ Netherlands
RegionNorth Holland
CityAmsterdam
TimezoneEurope/Amsterdam
Latitude52.13
Longitude5.29

๐Ÿข Ownership & Registration

OrganizationIP-RIPE
ASNAS210976
Network NameRU-TIMEWEB-20230627
CIDR Block91.240.254.0/25
RIRRIPE
CountryNL
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

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

๐Ÿ”Œ 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
13%
11
routing
13%
11
services
13%
11
ownership
30%
23
reputation
0%
00
geolocation
13%
11
Overall14%67
Coverage: 5/6 dimensions ยท Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-25 18:48:47 UTC
Last Seen2026-06-11 01:00:03 UTC
Profile Built2026-06-11 01:07:58 UTC
Data FreshnessLive
Signal Types16
Total Observations16
๐Ÿ” 16 signal types ยท 16 observations collected
This report is generated from 16+ 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.