IPDebrief

109.200.159.170

IP Intelligence Dossier
Your IP: 216.73.217.75

109.200.159.170 is an IPv4 address announced by AS6789, with approximate network location Russia. Its reverse DNS name is ip170-159-200-109.crelcom.network. As of November 12, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.

{ } JSON

🌍 Geolocation

Country🇷🇺 Russia
Location scopeApproximate network location. Distributed and anycast services can vary by observation point.
Anycast classificationUnverified (not proof of unicast)
Region—
City—
Timezone—
Latitude—
Longitude—

🏢 Ownership & Registration

Registered holderAS6789-MNT
ASNAS6789
Network NameTRK-ELAS-2
CIDR Block109.200.159.160/28
RIRARIN
Network registration countryRU
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRip170-159-200-109.crelcom.network
Forward ConfirmedNo — PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesip170-159-200-109.crelcom.network

DNS Posture

Results describe the queried names. SPF, DMARC and CAA are domain policies, not requirements for every IP. DNSSEC here describes reverse DNS; inconclusive validation does not mean unsigned.

Not assessed: 0 conclusive IP DNS checks.

spfNot checked
dmarcNot checked
fcrDnsNot checked
dnssecNot checked
caaNot checked

☁️ Network Classification

InfrastructureUnknown
Service PurposeWeb Server
Network TierUnknown — Insufficient routing data to classify
No specific classification

🔌 Services & Open Ports

PortServiceProtocolBanner
443httpstcp—
Closed Ports22, 25, 80, 3389, 8080, 8443 (1 open / 7 scanned)
ServerWeb server detected
HTTP Title—

🔐 TLS Certificate

Historical certificate; current certificate unknown. This describes the last probe, not a live check. An IP-targeted handshake does not establish the certificate served for every hostname.
🔒
CN=billing.sonet.online
Issued by CN=YR2, O=Let's Encrypt, C=US
Self-signed: No
SANsbilling.sonet.online
Valid From2026-10-16T15:36:18+00:00
Valid Until2027-01-14T15:36:17+00:00
TLS ProtocolTls12
Cipher SuiteTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period89 days

🛡️ Public Network Snapshot

Origin ASNAS6789
Network Prefix109.200.128.0/19
Route mappingFound
HSTSNot detected
CSPNot detected
HTTP/2Not detected

📅 Observation Timeline 🔄 Recent

First Seen2026-11-04 08:41:23 UTC
Last Seen2026-11-05 19:24:51 UTC
Profile Built2026-11-12 19:30:22 UTC
Data FreshnessRecent
Signal Types17
Total Observations17
🔍 17 signal types · 17 observations collected
This report is generated from 17+ 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 📧 Enterprise Access

❓ Frequently Asked Questions About 109.200.159.170

Who owns the IP address 109.200.159.170?

109.200.159.170 is registered to AS6789-MNT. The address falls within the 109.200.159.160/28 network block. Registration is held at ARIN.

Where is 109.200.159.170 located?

Geolocation data places 109.200.159.170 in Russia. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.

Is 109.200.159.170 malicious or safe?

109.200.159.170 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.

What is the hostname for 109.200.159.170?

The reverse DNS (PTR) record for 109.200.159.170 is ip170-159-200-109.crelcom.network. This hostname is not forward-confirmed, so it should be treated as a weak signal.

What ports are open on 109.200.159.170?

Responsive ports observed on 109.200.159.170 include 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.

🏘️ Related IP Addresses

Addresses sharing infrastructure

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.