4.34.16.30
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 (34y) +6
- Not on any threat blocklist +5
- Trust score 76 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- littleonline.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 900 s
- Reverse DNS last checked
- 2026-08-27 08:12 UTC
Forward DNS records for littleonline.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 141.193.213.20 | — | 3600s |
| A | 141.193.213.21 | — | 3600s |
| MX | littleonline-com.mail.protection.outlook.com | 0 | 172800s |
| NS | ns1-06.azure-dns.com | — | 172800s |
| NS | ns2-06.azure-dns.net | — | 172800s |
| NS | ns3-06.azure-dns.org | — | 172800s |
| NS | ns4-06.azure-dns.info | — | 172800s |
| TXT | MS=ms31961798 | — | 172800s |
| TXT | MS=ms93649333 | — | 172800s |
| TXT | ZOOM_verify_UW7TiWCkQyG15Lj7Jkf7Jg | — | 172800s |
| TXT | anthropic-domain-verification-epajxj=HfXzODRw5z6Hj3yJf94Htp5xd | — | 172800s |
| TXT | apple-domain-verification=Kcmn4QOG2QZhnJj2 | — | 172800s |
| TXT | atlassian-domain-verification=Sk9k/EIJfCfJuPVtV/I8SUwyE/Wav89lcZdFKDuTauhabQyfm7J5f3lsrTcXf4d/ | — | 172800s |
| TXT | atlassian-domain-verification=vzakA53MkZaE6Jnp5DezysO9oPilgofina2uMiU8cUlFeM66/Why6S6mVmr03OmB | — | 172800s |
| TXT | autodesk-domain-verification=Y1allFOGYxB6Tves5RMG | — | 172800s |
| TXT | logmein-verification-code=f805b4b8-9247-47db-a529-4e6c9bfc074a | — | 172800s |
| TXT | miro-verification=82658b0a1485dcd780ba56f9db41161c89e5668f | — | 172800s |
| TXT | n0kp1bic5tbd2qr4a5n7pq69ht | — | 172800s |
| TXT | openai-domain-verification=dv-iFGhO6nUzsUMzXhvMQuMZKCS | — | 172800s |
| TXT | sophos-domain-verification=ef8199da812622b199d51ee82c5e95fb9bd6f027b512dce68444961e3299ac68 | — | 172800s |
| TXT | sp-redirect.azurewebsites.net | — | 172800s |
| TXT | v=DMARC1; p=quarantine; pct=100 | — | 172800s |
| TXT | v=spf1 mx ip4:20.85.147.113 ip4:162.211.28.240 ip4:20.169.231.101 ip4:52.1.234.206 ip4:52.70.152.226 ip4:54.165.79.164 ip4:172.174.24.31 ip4:104.209.155.182 ip4:135.84.68.123 ip4:135.84.79.54 a:littleonline.com include:spf.protection.outlook.com include:spf.constantcontact.com include:_spf.ultipro.com include:_spf.createsend.com ~all | — | 172800s |
| TXT | zone=Y9l1ED0O9v-Z535SGq8p | — | 172800s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 4.34.16.30
- CIDR range
- 4.34.16.0/22
- IP range (int)
- 69,341,184 — 69,342,207
- Prefix length
- /22
- Organization
- Level 3 Parent, LLC
- ASN
- AS3356
- ASN name
- Level 3 Parent, LLC
- Location
- Charlotte, North Carolina, United States
- Coordinates
- 35.229600, -80.843000
- Accuracy radius
- 200 km
- Postal code
- 28202
- Regional Internet Registry
- ARIN
- Allocated
- 1992-12-01
- Data source(s)
- maxmind_city, maxmind_asn, maxmind_country, ipinfo_lite
- Last updated
- 2026-08-26 05:20:27
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 | — | US |
See the full history for 4.34.0.0/18.
Frequently Asked Questions
Who owns 4.34.16.30?
4.34.16.30 is allocated to Level 3 Parent, LLC (AS3356), registered in Charlotte, United States.
Where is 4.34.16.30 located?
The geolocation for 4.34.16.30 maps to Charlotte, 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 4.34.16.30 on?
4.34.16.30 belongs to the 4.34.16.0/22 network block announced by AS3356. This range contains 1,024 addresses.
Does 4.34.16.30 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.
