169.48.138.197 is an IPv4 address operated by SOFTLAYER - IBM Cloud, US (AS36351), with approximate network location Dallas, United States. As of November 13, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | IP Admin |
| ASN | AS36351 |
| Network Name | SOFTLAYER-RIPE-4-18-19-20 |
| CIDR Block | 169.45.0.0/16 |
| RIR | ARIN |
| Network registration country | NL |
| Routing operator | SOFTLAYER - IBM Cloud, US |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
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.
| caa | Not checked |
| spf | Not checked |
| dmarc | Not checked |
| dnssec | Not checked |
| fcrDns | Not checked |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| Closed Ports | 22, 25, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| Port | Probe target | Certificate finding |
|---|---|---|
| (IP-targeted) | CN=*.swiftype.com, O="Elasticsearch, Inc.", L=Mountain View, S=California, C=US Historical certificate; current certificate unknown |
| SANs | *.swiftype.comswiftype.com |
| Valid From | 2026-06-03T00:00:00+00:00 |
| Valid Until | 2026-12-18T23:59:59+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 198 days |
🛡️ Public Network Snapshot
| Origin ASN | AS36351 |
| Network Prefix | 169.48.128.0/18 |
| Route mapping | Found |
| HSTS | Not detected |
| CSP | Not detected |
| HTTP/2 | Not detected |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 25% | 1 | 2 |
| reputation | 0% | 0 | 0 |
| geolocation | 25% | 1 | 1 |
| Overall | 20% | 5 | 6 |
| Data Coherence | Consistent (100%) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Aging
| First Seen | 2026-10-17 15:09:33 UTC |
| Last Seen | 2026-11-01 15:16:23 UTC |
| Profile Built | 2026-11-13 07:30:05 UTC |
| Data Freshness | Aging |
| Signal Types | 24 |
| Total Observations | 26 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 169.48.138.197
Who owns the IP address 169.48.138.197?
169.48.138.197 is registered to IP Admin. The address falls within the 169.45.0.0/16 network block. Registration is held at ARIN.
Where is 169.48.138.197 located?
Geolocation data places 169.48.138.197 in Dallas, TX, United States. The local time zone is America/Chicago. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 169.48.138.197 malicious or safe?
169.48.138.197 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 ports are open on 169.48.138.197?
Responsive ports observed on 169.48.138.197 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.