74.48.46.88
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
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- ccbchurch.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 86400 s
- Reverse DNS last checked
- 2026-09-19 19:11 UTC
Forward DNS records for ccbchurch.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 104.16.16.2 | — | 300s |
| A | 104.16.17.2 | — | 300s |
| AAAA | 2606:4700::6810:1002 | — | 172796s |
| AAAA | 2606:4700::6810:1102 | — | 172796s |
| MX | mail-in.ccbchurch.com | 10 | — |
| NS | erin.ns.cloudflare.com | — | — |
| NS | ian.ns.cloudflare.com | — | — |
| TXT | google-site-verification=B4kOehmJidXKye25v9TvWlF-qmDxOMmeU4SqGusfF9I | — | — |
| TXT | google-site-verification=cQFLJY2oLvqJTPYeeM2_bh6OBbGIgQWJD4yzDBDLu5M | — | — |
| TXT | v=DMARC1; p=quarantine; rua=mailto:dabd2b166a184d438b5ce9dffc282523@dmarc-reports.cloudflare.net,mailto:dmarc_agg@vali.email; | — | — |
| TXT | v=spf1 ip4:34.208.94.28 ip4:34.212.58.106 ip4:34.213.214.151 ip4:34.215.18.110 ip4:18.188.48.108 ip4:18.223.127.243 ip4:18.224.126.69 ip4:18.224.42.96 ip4:3.16.0.99 ~all | — | — |
| TXT | yahoo-verification-key=qSCLuRvFtp+vmhsOo0qydfxytVhYn3108jxzyV7riis= | — | — |
| CAA | iodef mailto:sys-admins@churchcommunitybuilder.com | 0 | — |
| CAA | issue amazon.com | 0 | — |
| CAA | issue amazonaws.com | 0 | — |
| CAA | issue amazontrust.com | 0 | — |
| CAA | issue awstrust.com | 0 | — |
| CAA | issue comodoca.com | 0 | — |
| CAA | issue digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issue globalsign.com | 0 | — |
| CAA | issue letsencrypt.org | 0 | — |
| CAA | issue pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issue ssl.com | 0 | — |
| CAA | issuewild amazon.com | 0 | — |
| CAA | issuewild amazonaws.com | 0 | — |
| CAA | issuewild amazontrust.com | 0 | — |
| CAA | issuewild awstrust.com | 0 | — |
| CAA | issuewild comodoca.com | 0 | — |
| CAA | issuewild digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild globalsign.com | 0 | — |
| CAA | issuewild letsencrypt.org | 0 | — |
| CAA | issuewild pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild ssl.com | 0 | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 74.48.46.88
- CIDR range
- 74.48.46.0/23
- IP range (int)
- 1,244,671,488 — 1,244,671,999
- Prefix length
- /23
- Organization
- MULTACOM CORPORATION
- ASN
- AS35916
- ASN name
- MULTACOM CORPORATION
- Location
- Los Angeles, California, United States
- Coordinates
- 34.054400, -118.244000
- Accuracy radius
- 20 km
- Postal code
- 90060
- Regional Internet Registry
- ARIN
- Allocated
- 2006-02-09
- Data source(s)
- ipinfo_lite, maxmind_city, maxmind_country, maxmind_asn
- Last updated
- 2026-09-20 06:07:58
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 weekly from regional internet registry (RIR) delegation files for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | New Allocation | — | CA |
See the full history for 74.48.0.0/17.
Frequently Asked Questions
Who owns 74.48.46.88?
74.48.46.88 is allocated to MULTACOM CORPORATION (AS35916), registered in Los Angeles, United States.
Where is 74.48.46.88 located?
The geolocation for 74.48.46.88 maps to Los Angeles, 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 74.48.46.88 on?
74.48.46.88 belongs to the 74.48.46.0/23 network block announced by AS35916. This range contains 512 addresses.
Does 74.48.46.88 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.
