Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
191.7.35.0/24 ·
Warning: 191.7.35.0/24 is announced by AS1 (LVLT-1), AS4 (ISI-AS). 6 warnings
| Announced as | 191.7.35.0/24 |
|---|---|
| Origin AS | AS1 LVLT-1 AS4 ISI-AS |
| Holder | LaraNet Telecomunicações e Serviços EIRALI |
| Allocation | LACNIC, Brazil (BR), allocated 2014-02-19 |
| Size | 256 addresses |
| Abuse contact | jean@teeb.com.br |
What to fix
-
Warning
More than one origin AS (MOAS).
Sometimes intended (anycast, DDoS scrubbing), sometimes a hijack or leak. Check the origins are all yours.
-
Warning
191.7.35.0/24 from AS1 is RPKI not found: no ROA covers it.
Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.
Fix: Create a ROA for this prefix with origin AS1 and a max length equal to the prefix length.
prefix: 191.7.35.0/24 origin: AS1 max-length: 24
-
Warning
191.7.35.0/24 from AS4 is RPKI not found: no ROA covers it.
Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.
Fix: Create a ROA for this prefix with origin AS4 and a max length equal to the prefix length.
prefix: 191.7.35.0/24 origin: AS4 max-length: 24
-
Warning
No IRR route object for 191.7.35.0/24 with origin AS1.
Many networks build their prefix filters from IRR data; without a route object some of them drop the route.
Fix: Create a route object in your RIR’s IRR database (or RADB):
route: 191.7.35.0/24 origin: AS1
-
Warning
No IRR route object for 191.7.35.0/24 with origin AS4.
Many networks build their prefix filters from IRR data; without a route object some of them drop the route.
Fix: Create a route object in your RIR’s IRR database (or RADB):
route: 191.7.35.0/24 origin: AS4
-
Warning
Reverse DNS is not delegated for 191.7.35.0/24, so its addresses have no PTR records.
Mail receivers look up the PTR of the sending address and reject or spam-score mail without one; traceroutes and logs show bare numbers.
Fix: Create the reverse zones (domain objects for in-addr.arpa or ip6.arpa) at your RIR, pointing at your nameservers, or ask your provider to set PTR records.
Checks
Routing and RPKI More than one origin AS (MOAS).
- Pass: Announced as 191.7.35.0/24 by AS1, AS4.
- Warning: More than one origin AS (MOAS).
- Warning: 191.7.35.0/24 from AS1 is RPKI not found: no ROA covers it.
- Warning: 191.7.35.0/24 from AS4 is RPKI not found: no ROA covers it.
- Warning: No IRR route object for 191.7.35.0/24 with origin AS1.
- Warning: No IRR route object for 191.7.35.0/24 with origin AS4.
- Pass: Seen by 100% of RIPE RIS peers.
Source: RIPEstat (RIPE NCC RIS, Routinator)
Open in ASN & BGP prefix lookupReverse DNS Reverse DNS is not delegated for 191.7.35.0/24, so its addresses have no PTR records.
- Warning: Reverse DNS is not delegated for 191.7.35.0/24, so its addresses have no PTR records.
| Zone | Nameservers |
|---|---|
| 35.7.191.in-addr.arpa | Not delegated |
Registration Found at rdap.lacnic.net.
- Pass: Found at rdap.lacnic.net.
| Name | 489431 |
|---|---|
| Handle | 191.7.35.0/24 |
| Range | 191.7.35.0 – 191.7.35.255 |
| Country | BR |
| Status | active |
| Registered | 2014-02-19T10:17:05Z |
| Last changed | 2024-06-24T11:01:20Z |
| Abuse contact | jean@teeb.com.br |
| Registry (RIR) | LACNIC |
|---|---|
| Country | Brazil (BR) |
| Delegated on | 2014-02-19 |
| Status | Allocated |
| Delegated range | 191.7.35.0/24 (191.7.35.0 – 191.7.35.255) |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | LaraNet Telecomunicações e Serviços EIRALI | |
| technical, abuse | Jean Elvis Frota | jean@teeb.com.br |
Source: https://rdap.lacnic.net/rdap/ip/191.7.35.0/24. Registration data from rdap.lacnic.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB PeeringDB did not answer: HTTP 404
- Warning: PeeringDB did not answer: HTTP 404
About the network that announces this space, so not in the fix list.
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup