Skip to content
thenetworkery

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.

IP address, prefix or AS number

206.84.236.0/24 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=206.84.236.0%2F24"
JSON Docs

Warning: 206.84.236.0/24 is announced by AS136334 (VNPL-AS). 2 warnings

Announced as206.84.236.0/24
Origin ASAS136334 VNPL-AS
HolderVortex Netsol Private Limited
AllocationARIN, United States (US), allocated 1995-08-10
Size256 addresses

What to fix

  1. Warning

    Reverse DNS is not delegated for 206.84.236.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.

    Open in DNS lookup

  2. Warning

    No abuse contact is published for 206.84.236.0/24.

    Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.

    Fix: Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC.

    Open in WHOIS / RDAP lookup

Checks

Routing and RPKI Announced as 206.84.236.0/24 by AS136334.
  • Pass: Announced as 206.84.236.0/24 by AS136334.
  • Pass: 206.84.236.0/24 from AS136334 is RPKI valid.
  • Pass: Seen by 100% of RIPE RIS peers.
  • Info: The ROA 206.84.224.0/20 AS136334 allows announcements up to /24.
Route206.84.236.0/24
Origin ASAS136334 VNPL-AS - Vortex Netsol Private Limited RPKI valid
IRR route objectsARIN, RADB
Visibility (RIS peers)318 / 319
First seen2021-01-27
Covering prefixes206.84.0.0/15
ROAs covering this prefix
ROA prefixMax lengthOrigin AS
206.84.224.0/20 /24 AS136334

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 206.84.236.0/24, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 206.84.236.0/24, so its addresses have no PTR records.
Reverse zones 1
ZoneNameservers
236.84.206.in-addr.arpa Not delegated
Open in DNS lookup
Registration No abuse contact is published for 206.84.236.0/24.
  • Pass: Found at rdap.arin.net.
  • Warning: No abuse contact is published for 206.84.236.0/24.
NameVORTEX-NETSOL-CGNT-NET-1
HandleNET-206-84-224-0-1
Range206.84.224.0 – 206.84.239.255
Statusactive
Registered2021-02-11T10:00:21-05:00
Last changed2021-02-11T10:00:21-05:00
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on1995-08-10
StatusAllocated
Delegated range206.84.0.0/15 (206.84.0.0 – 206.85.255.255)

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant Vortex Netsol Private Limited

Source: https://rdap.arin.net/registry/ip/206.84.236.0/24. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB AS136334 is in PeeringDB as VORTEX NETSOL PRIVATE LIMITED.
  • Pass: AS136334 is in PeeringDB as VORTEX NETSOL PRIVATE LIMITED.
  • Info: Peering policy: Open.
  • Info: Present at 4 internet exchanges with 4 ports (45G in total).

About the network that announces this space, so not in the fix list.

NetworkVORTEX NETSOL PRIVATE LIMITED
AS numberAS136334
TypeContent, Regional
Websitehttp://www.vortexnetsol.com
IRR as-setAS136334:AS-VORTEX-CUSTOMERS
Prefixes (IPv4 / IPv6)2000 / 1000
Traffic300-500Gbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2025-08-31
Contacts
Technicalprasad@vortexnetsol.com
NOCmumbainoc@vortexnetsol.com
Policyprasad@vortexnetsol.com
Abuseabuse@vortexnetsol.com

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup