Reputation · trust score
A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.
- Baseline (neutral) 65
- Forward-confirmed reverse DNS (FCrDNS) +10
- Long-established allocation (26y) +6
- Not on any threat blocklist +5
- Enterprise allocation +4
- Trust score 90 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- bmta.outgoing.linkdatacenter.net
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 60 s
- Reverse DNS last checked
- 2026-10-22 07:28 UTC
- Forward DNS last checked
- 2026-10-22 07:28 UTC
Forward DNS records for bmta.outgoing.linkdatacenter.net
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 196.205.23.148 | — | 60s |
| A | 196.205.62.85 | — | 3600s |
| A | 196.205.93.104 | — | 60s |
| A | 196.205.93.105 | — | 172800s |
| A | 196.205.93.106 | — | 172800s |
| A | 196.205.93.109 | — | 3600s |
| A | 196.205.93.111 | — | 3600s |
| A | 196.205.93.114 | — | 258s |
| A | 196.205.93.116 | — | 3600s |
| A | 196.205.93.99 | — | 60s |
| A | 41.178.15.108 | — | 3600s |
| A | 41.178.15.117 | — | 60s |
| A | 41.178.15.131 | — | 3600s |
| A | 41.178.15.167 | — | 172800s |
| A | 41.178.15.241 | — | 60s |
| A | 41.178.15.83 | — | 3600s |
| A | 41.178.15.85 | — | 60s |
| A | 41.178.51.207 | — | 3600s |
| A | 41.178.51.208 | — | 60s |
| A | 41.178.51.79 | — | 60s |
| A | 41.196.200.113 | — | 60s |
| A | 41.196.200.145 | — | 3600s |
| A | 41.196.200.146 | — | 3600s |
| A | 41.196.200.215 | — | 172783s |
| A | 41.196.200.216 | — | 172783s |
| A | 41.196.200.221 | — | 60s |
| A | 41.196.200.222 | — | 300s |
| A | 41.196.200.34 | — | 172783s |
| A | 41.196.200.62 | — | 60s |
| A | 41.196.200.87 | — | 172800s |
| A | 62.241.134.47 | — | 3600s |
| A | 62.241.134.48 | — | 60s |
| A | 62.241.134.54 | — | 3600s |
| A | 62.241.134.55 | — | 3600s |
| A | 62.241.134.58 | — | 3600s |
| A | 62.241.134.60 | — | 3600s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Domains hosted
as of 2026-10-18 UTC0
issued.live's latest DNS data shows no domain resolving to this IP.
Domain data provided by issued.live — for full details visit https://issued.live/pricing
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
- bmta.outgoing.linkdatacenter.net — Oct 15, 2026 → present
- no PTR — Oct 15, 2026 → Oct 15, 2026
- bmta.outgoing.LINKDATACENTER.NET — Sep 28, 2026 → Oct 15, 2026
- no PTR — Sep 27, 2026 → Sep 28, 2026
- bmta.outgoing.linkdatacenter.net — Aug 18, 2026 → Sep 27, 2026
- host-196-205-23-148.static.link.com.eg — Jun 4, 2026 → Aug 18, 2026
Network Allocation for 196.205.23.148
- CIDR range
- 196.205.0.0/16
- IP range (int)
- 3,301,769,216 — 3,301,834,751
- Prefix length
- /16
- Organization
- Link Egypt (Link.NET)
- ASN
- AS24863
- ASN name
- Link Egypt (Link.NET)
- Location
- Egypt
- Coordinates
- 30.035500, 31.223000
- Accuracy radius
- 100 km
- Regional Internet Registry
- AFRINIC
- Allocated
- 2000-03-28
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-10-21 08:48:23
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
Frequently Asked Questions
Who owns 196.205.23.148?
196.205.23.148 is allocated to Link Egypt (Link.NET) (AS24863), registered in Egypt.
Where is 196.205.23.148 located?
The geolocation for 196.205.23.148 maps to Egypt based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.
What network is 196.205.23.148 on?
196.205.23.148 belongs to the 196.205.0.0/16 network block announced by AS24863. This range contains 65,536 addresses.
Does 196.205.23.148 have a reverse DNS record?
Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.
Neighbors
Other addresses in the same /24.
