IPDebrief

176.126.104.21

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

Intelligence analysis identified IP 176.126.104.21 as belonging to AS46475 (ALAXONA) within the FINEGROUPSERVERS-LEASE CIDR block in Russia. The asset was observed between July 11, 2026, and September 3, 2026, maintaining a Low Risk reputation with a risk score of 0. No malicious indicators were present; the address is not listed on blacklists, is not a known attacker, and is not associated with Tor or spam campaigns. Service reconnaissance confirmed the host was firewalled with no open ports. Network hygiene showed a Poor score of 20 due to missing SPF and DMARC records. While the broader neighborhood classification remained mostly clean, one threat sibling existed within the subnet. The asset exhibits minimal threat persistence. Based on the absence of significant risk indicators, the recommendation was to Allow traffic with Info severity.

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

🌍 Geolocation

Country🇷🇺 Russia
Region—
City—
Timezone—
Latitude—
Longitude—

🏢 Ownership & Registration

OrganizationALAXONA
ASNAS46475
Network NameFINEGROUPSERVERS-LEASE
CIDR Block176.126.104.0/25
RIRRIPE
CountryRU
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
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 ASNAS46475
Network Prefix176.126.104.0/24
Route mappingFound

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
31%
25
routing
8%
11
services
12%
22
ownership
23%
24
reputation
31%
15
geolocation
17%
23
Overall20%1020
Coverage: 5/6 dimensions · Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

📅 Observation Timeline 🔄 Live

First Seen2026-07-11 14:30:16 UTC
Last Seen2026-09-04 22:17:48 UTC
Profile Built2026-09-04 22:20:01 UTC
Data FreshnessLive
Signal Types20
Total Observations27
🔍 20 signal types · 27 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

❓ Frequently Asked Questions About 176.126.104.21

Who owns the IP address 176.126.104.21?

176.126.104.21 is registered to ALAXONA. The address falls within the 176.126.104.0/25 network block. Registration is held at RIPE.

Where is 176.126.104.21 located?

Geolocation data places 176.126.104.21 in Russia. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.

Is 176.126.104.21 malicious or safe?

176.126.104.21 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.

🏘️ Related IP Addresses

Nearby addresses in 176.126.104.0/25

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.