75.61.95.3
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
- Long-established allocation (20y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Isp allocation +5
- Trust score 86 / 100
Experimental · trust-vectors model v1.3.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- ns2.filelan.com.0/26.95.61.75.in-addr.arpa
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-11-09 19:31 UTC
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Domains hosted
as of 2026-11-12 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.
This IP's reverse DNS changes frequently — the timeline below shows the most recent changes.
- ns2.filelan.com.0/26.95.61.75.in-addr.arpa — Nov 9, 2026 → present
- email.filelan.com — Nov 8, 2026 → Nov 9, 2026
- ns2.filelan.com.0/26.95.61.75.in-addr.arpa — Nov 4, 2026 → Nov 8, 2026
- email.filelan.com — Nov 3, 2026 → Nov 4, 2026
- ns2.filelan.com.0/26.95.61.75.in-addr.arpa — Nov 1, 2026 → Nov 3, 2026
- email.filelan.com — Oct 30, 2026 → Nov 1, 2026
- ns2.filelan.com.0/26.95.61.75.in-addr.arpa — Oct 29, 2026 → Oct 30, 2026
- email.filelan.com — Oct 28, 2026 → Oct 29, 2026
- ns2.filelan.com.0/26.95.61.75.in-addr.arpa — Oct 27, 2026 → Oct 28, 2026
- no PTR — Oct 26, 2026 → Oct 27, 2026
- ns2.filelan.com.0/26.95.61.75.in-addr.arpa — Oct 24, 2026 → Oct 26, 2026
- email.filelan.com — Oct 23, 2026 → Oct 24, 2026
- ns2.filelan.com.0/26.95.61.75.in-addr.arpa — Oct 22, 2026 → Oct 23, 2026
- email.filelan.com — Oct 16, 2026 → Oct 22, 2026
- ns2.filelan.com.0/26.95.61.75.in-addr.arpa — Oct 12, 2026 → Oct 16, 2026
- email.filelan.com — Oct 1, 2026 → Oct 12, 2026
- no PTR — Sep 30, 2026 → Oct 1, 2026
- ns2.filelan.com.0/26.95.61.75.in-addr.arpa — Sep 29, 2026 → Sep 30, 2026
- email.filelan.com — Sep 27, 2026 → Sep 29, 2026
- ns2.filelan.com.0/26.95.61.75.in-addr.arpa — Sep 26, 2026 → Sep 27, 2026
- email.filelan.com — Sep 25, 2026 → Sep 26, 2026
- no PTR — Aug 23, 2026 → Sep 25, 2026
- email.filelan.com — Jun 1, 2026 → Aug 23, 2026
Network Allocation for 75.61.95.3
- CIDR range
- 75.61.92.0/22
- IP range (int)
- 1,262,312,448 — 1,262,313,471
- Prefix length
- /22
- Organization
- AT&T Enterprises, LLC
- ASN
- AS7018
- ASN name
- AT&T Enterprises, LLC
- Location
- Tulsa, Oklahoma, United States
- Coordinates
- 36.060600, -95.945600
- Accuracy radius
- 500 km
- Postal code
- 74136
- Regional Internet Registry
- ARIN
- Allocated
- 2006-02-28
- Data source(s)
- maxmind_city, maxmind_asn, maxmind_country, ipinfo_lite
- Last updated
- 2026-11-11 08:44:39
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
RIR Ownership History
Atom feed ⇲Allocation changes captured from regional internet registry (RIR) delegation files, re-imported every six hours, for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | New Allocation | — | US |
See the full history for 75.56.0.0/13.
Frequently Asked Questions
Who owns 75.61.95.3?
75.61.95.3 is allocated to AT&T Enterprises, LLC (AS7018), registered in Tulsa, United States.
Where is 75.61.95.3 located?
The geolocation for 75.61.95.3 maps to Tulsa, United States 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 75.61.95.3 on?
75.61.95.3 belongs to the 75.61.92.0/22 network block announced by AS7018. This range contains 1,024 addresses.
Does 75.61.95.3 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.
