IPDebrief

109.75.172.153

IP Intelligence Dossier
Your IP: 216.73.217.131
{ } JSON 🔧 Full Actions API

🌍 Geolocation

Country🇺🇸 United States
RegionUS-MA
CityBoston
TimezoneAmerica/New_York
Latitude42.36
Longitude-71.06

🏢 Ownership & Registration

OrganizationHyperslice Network Team
ASNAS31727
Network NameHyperslice-Customer
CIDR Block109.75.172.0/24
RIRARIN
CountryGB
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRserver6.digigate.net
Forward ConfirmedNo — PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesserver6.digigate.net

🔐 DNS Hygiene

Hygiene Score60% (Good)
SPFPresent
DMARCPresent
FCrDNSNot verified
DNSSECValid
CAANot configured

☁️ Network Classification

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

🔌 Services & Open Ports

PortServiceProtocolBanner
80httptcp—
443httpstcp—
22sshtcpBanner detected
8443https-alttcp—
Closed Ports25, 3389, 8080 (4 open / 7 scanned)
ServerWeb server detected
HTTP Title—

🔐 TLS Certificate

An expired certificate for CN=server6.digigate.net was found on this IP. This may indicate a previously hosted website, a decommissioned service, or stale infrastructure.
🔒
CN=server6.digigate.net
Issued by CN=R13, O=Let's Encrypt, C=US
Self-signed: No
SANsserver6.digigate.net
Valid From2026-05-28T13:25:42+00:00
Valid Until2026-08-26T13:25:41+00:00 (expired)
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period89 days

🛡️ Public Network Snapshot

Origin ASNAS31727
Network Prefix109.75.172.0/24
Route mappingFound
Certificates in transparency logs0 certificates
HSTSNot detected
CSPNot detected
HTTP/2Enabled

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
25%
11
routing
25%
11
services
25%
11
ownership
0%
00
reputation
0%
00
geolocation
25%
11
Overall16%44
Coverage: 4/6 dimensions · Data sufficiency: partial
Data CoherenceMixed Signals (68%) — 2 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Geo sources disagree on country: CH, GB, US
⚠ TLS certificate claims CH but primary geo says US

📅 Observation Timeline 🔄 Live

First Seen2026-06-08 08:01:39 UTC
Last Seen2026-07-18 03:20:55 UTC
Profile Built2026-08-29 02:52:01 UTC
Data FreshnessLive
Signal Types21
Total Observations23
🔍 21 signal types · 23 observations collected
This report is generated from 21+ 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 109.75.172.153

Who owns the IP address 109.75.172.153?

109.75.172.153 is registered to Hyperslice Network Team. The address falls within the 109.75.172.0/24 network block. Registration is held at ARIN.

Where is 109.75.172.153 located?

Geolocation data places 109.75.172.153 in Boston, US-MA, United States. The local time zone is America/New_York. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.

Is 109.75.172.153 malicious or safe?

109.75.172.153 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.75.172.153?

The reverse DNS (PTR) record for 109.75.172.153 is server6.digigate.net. This hostname is not forward-confirmed, so it should be treated as a weak signal.

What ports are open on 109.75.172.153?

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

🏘️ Related IP 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.