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.
186.226.167.0/24 ·
Warning: 186.226.167.0/24 is announced by AS53180 (AS53180). 2 warnings
| Announced as | 186.226.167.0/24 |
|---|---|
| Origin AS | AS53180 AS53180 |
| Holder | INFORTEL COMUNICACOES LTDA |
| Allocation | LACNIC, Brazil (BR), allocated 2010-08-13 |
| Size | 256 addresses |
| Abuse contact | getulio2013@hotmail.com |
What to fix
-
Warning
Seen by only 16% of RIPE RIS peers.
Partial visibility points to filtering, a missing IRR route object, or an RPKI problem.
-
Warning
Reverse DNS is not delegated for 186.226.167.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 Seen by only 16% of RIPE RIS peers.
- Pass: Announced as 186.226.167.0/24 by AS53180.
- Pass: 186.226.167.0/24 from AS53180 is RPKI valid.
- Warning: Seen by only 16% of RIPE RIS peers.
| Route | 186.226.167.0/24 |
|---|---|
| Origin AS | AS53180 AS53180 - INFORTEL COMUNICACOES LTDA RPKI valid |
| IRR route objects | RADB |
| Visibility (RIS peers) | 52 / 321 |
| First seen | 2013-11-16 |
| Covering prefixes | 186.226.166.0/23, 186.226.164.0/22, 186.226.160.0/21, 186.226.160.0/20 |
| ROA prefix | Max length | Origin AS |
|---|---|---|
| 186.226.167.0/24 | /24 | AS53180 |
| 186.226.166.0/23 | /23 | AS53180 |
| 186.226.164.0/22 | /22 | AS53180 |
| 186.226.160.0/21 | /21 | AS53180 |
| 186.226.160.0/20 | /20 | AS53180 |
Source: RIPEstat (RIPE NCC RIS, Routinator)
Open in ASN & BGP prefix lookupReverse DNS Reverse DNS is not delegated for 186.226.167.0/24, so its addresses have no PTR records.
- Warning: Reverse DNS is not delegated for 186.226.167.0/24, so its addresses have no PTR records.
| Zone | Nameservers |
|---|---|
| 167.226.186.in-addr.arpa | Not delegated |
Registration Found at rdap.lacnic.net.
- Pass: Found at rdap.lacnic.net.
| Name | 148716 |
|---|---|
| Handle | 186.226.160.0/20 |
| Range | 186.226.160.0 – 186.226.175.255 |
| Country | BR |
| Status | active |
| Registered | 2010-08-13T12:37:35Z |
| Last changed | 2021-07-26T13:04:41Z |
| Abuse contact | getulio2013@hotmail.com |
| Registry (RIR) | LACNIC |
|---|---|
| Country | Brazil (BR) |
| Delegated on | 2010-08-13 |
| Status | Allocated |
| Delegated range | 186.226.160.0/20 (186.226.160.0 – 186.226.175.255) |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | INFORTEL COMUNICACOES LTDA | |
| technical, abuse | Getulio Gonçalves Olimpio | getulio2013@hotmail.com |
Source: https://rdap.lacnic.net/rdap/ip/186.226.167.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 AS53180 is in PeeringDB as Infortel Comunicacoes.
- Pass: AS53180 is in PeeringDB as Infortel Comunicacoes.
- Info: Peering policy: Open.
- Info: Present at 7 internet exchanges with 10 ports (931G in total).
About the network that announces this space, so not in the fix list.
| Network | Infortel Comunicacoes (Infortel Telecom) |
|---|---|
| AS number | AS53180 |
| Type | NSP, Regional |
| Website | https://www.infortel.net.br |
| IRR as-set | AS53180:AS-ALL |
| Prefixes (IPv4 / IPv6) | 2000 / 2000 |
| Traffic | 500-1000Gbps, Mostly Inbound |
| Peering policy | Open |
| Policy URL | https://peering.infortel.net.br |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Looking glass | https://lg.infortel.net.br |
| Last updated | 2026-07-16 |
| NOC | noc@infortel.net.br |
|---|
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup